How to integrate Ignisign MCP with Claude Code

GET STARTED FOR FREE
Framework Integration Gradient
Ignisign Logo
Claude Code Logo
divider

Introduction

Manage your Ignisign directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Rube - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Why Rube?

Rube is a universal MCP server with access to 850+ SaaS apps. It ensures just-in-time tool loading so Claude can access the tools it needs, a remote workbench for programmatic tool calling and handling large tool responses out of the LLM context window, ensuring the LLM context window remains clean.

Connect Ignisign to Claude Code with Rube

1. Get the MCP URL

Copy and paste the below command in Claude Code to add Rube MCP.

Terminal

2. Authenticate Rube

Run /mcp to view Rube

bash
/mcp
Run /mcp to view Rube in Claude Code
Click on Rube to authenticate
Authentication flow complete

3. Ensure it's connected

Run /mcp again to verify the connection. Now, do whatever you want with Claude Code and Ignisign.

Rube connected successfully

Supported Tools & Triggers

Tools
Ignisign API AuthenticationTool to authenticate an application over Ignisign API and retrieve a JWT.
Cancel Signature RequestTool to cancel a signature request.
Initialize DocumentTool to initialize a document for a signature request.
Create SignerTool to create a new signer.
Create Webhook EndpointTool to create a new webhook endpoint for an application.
Delete DocumentTool to delete a specific document by its ID.
Delete Ignisign Signature RequestTool to delete a signature request.
Delete SignerTool to delete a signer.
Delete Webhook EndpointTool to delete a specific webhook endpoint.
Get application contextTool to retrieve the global context of an application.
Get Document InformationTool to retrieve document metadata by ID.
Get Missing Signer InputsTool to determine missing inputs needed for a signer in a specific signature profile.
Get Signature Request DetailsTool to retrieve detailed information for a specific signature request.
Get Signature Request DocumentTool to retrieve the document associated with a specific signature request.
Get Signature RequestsTool to retrieve a paginated list of signature requests for an application.
Get Signature Request StatusTool to retrieve the current status of a specific signature request.
Get Signed DocumentTool to download the signed document (signature proof) for a signature request.
Get Signer Creation ConstraintsTool to retrieve input constraints required to create a signer for a specific signature profile.
Get Signer Input ConstraintsTool to get signer input constraints.
Get Signer InputsTool to retrieve inputs provided by a signer for a signature request.
Get Signer ProfileTool to retrieve a signer profile.
Get Signer ProfilesTool to retrieve signer profiles.
Get Webhook DetailsTool to retrieve details of a specific webhook endpoint.
Get WebhooksTool to list all webhook endpoints configured for an application environment.
Close Ignisign Signature RequestTool to close an active signature request.
Update SignerTool to update details of an existing signer.
Initialize Ignisign Signature RequestTool to initialize a new signature request.
List DocumentsTool to retrieve documents linked to a signature request.
Provide Document Content Data JSONTool to provide JSON content for a document.
Provide Document Content FileTool to provide file content for a document.
Provide Document Content Private FileTool to provide private content for a document via its SHA-256 hash.
Publish Signature RequestTool to publish a draft signature request.
Search SignersTool to search for signers within an application.
Update Document InformationTool to update document metadata.
Update Signature RequestTool to partially update a signature request in DRAFT state.
Update Webhook EndpointTool to update an existing webhook endpoint.

What is the Ignisign MCP server, and what's possible with it?

The Ignisign MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ignisign account. It provides structured and secure access to your electronic signature workflows, so your agent can perform actions like sending signature requests, managing documents, onboarding signers, and handling signature operations on your behalf.

  • Automated signature request management: Let your agent create, cancel, or delete signature requests, streamlining the entire e-signature process from start to finish.
  • Document initialization and deletion: Have the agent initialize new documents for signing or permanently delete documents when they're no longer needed.
  • Signer onboarding and removal: Effortlessly add new signers to your application environment or remove existing ones as your workflows change.
  • Webhook endpoint management: Allow your agent to create or delete webhook endpoints, enabling real-time notifications and integrations for signature events.
  • Application context retrieval: Fetch global application settings and environment configurations so your agent always works with up-to-date information.

Connecting Ignisign via Tool Router

Tool Router is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Ignisign) for even more tool search precision. It's secure and reliable.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Ignisign account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["ignisign"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http ignisign-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Ignisign. This URL will be used to connect Claude Code to Ignisign.

What's happening:
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Ignisign
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Ignisign MCP to Claude Code

bash
claude mcp add --transport http ignisign-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (ignisign-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Ignisign MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your ignisign-composio entry in the list
  • This confirms that Claude Code can now access Ignisign tools

If everything is wired up, you should see your ignisign-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Ignisign

The first time you try to use Ignisign tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Ignisign
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Ignisign authorization flow
  • Return to the terminal and start using Ignisign through Claude Code

Once authenticated, you can ask Claude Code to perform Ignisign operations in natural language. For example:

  • "Start a new signature request for a contract"
  • "Add a new signer to this application"
  • "Delete a completed document by its ID"

Complete Code

Here's the complete code to get you started with Ignisign and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["ignisign"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http ignisign-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Ignisign with Claude Code using Composio's MCP server. Now you can interact with Ignisign directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Ignisign operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Ignisign operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Ignisign MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Ignisign MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Ignisign MCP with Claude Agent SDK

Google ADK

Google ADK

Use Ignisign MCP with Google ADK

LangChain

LangChain

Use Ignisign MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Ignisign MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Ignisign MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Ignisign MCP with LlamaIndex

CrewAI

CrewAI

Use Ignisign MCP with CrewAI

Codex

Codex

Use Ignisign MCP with Codex

FAQ

What are the differences in Tool Router MCP and Ignisign MCP?

With a standalone Ignisign MCP server, the agents and LLMs can only access a fixed set of Ignisign tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ignisign and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Ignisign tools.

Can I manage the permissions and scopes for Ignisign while using Tool Router?

Yes, absolutely. You can configure which Ignisign scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Ignisign data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free