How to integrate Ignisign MCP with Claude Agent SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Ignisign Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Ignisign to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Ignisign agent that can start a new signature request for a contract, add a new signer to this application, delete a completed document by its id, create a webhook to track signature events through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Ignisign account through Composio's Ignisign MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Ignisign
  • Configure an AI agent that can use Ignisign as a tool
  • Run a live chat session where you can ask the agent to perform Ignisign operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

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 Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

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:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Ignisign account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Ignisign functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Ignisign
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["ignisign"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Ignisign
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Ignisign tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Ignisign
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

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

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Ignisign
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["ignisign"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Ignisign tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Ignisign through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Ignisign MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Ignisign MCP with OpenAI Agents 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

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 Agent SDK?

Yes, you can. Claude Agent SDK 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
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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