How to integrate Ignisign MCP with CrewAI

This guide walks you through connecting Ignisign to CrewAI 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 through natural language commands. This guide will help you understand how to give your CrewAI 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.

Get started for free Get a demo

Ignisign

Api Key

Ignisign is an electronic signature platform for secure online document signing and management. Streamline agreements and digital paperwork with advanced workflow tools.

32 Tools

Managed auth

Connect Ignisign without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

This guide will help you understand how to give your CrewAI 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.

Also integrate Ignisign with

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI LlamaIndex

TL;DR

Here's what you'll learn:

Get a Composio API key and configure your Ignisign connection
Set up CrewAI with an MCP enabled agent
Create a Tool Router session or standalone MCP server for Ignisign
Build a conversational loop where your agent can execute Ignisign operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

Agent Roles: Define specialized agents with specific goals and backstories
Task Management: Create tasks with clear descriptions and expected outputs
Crew Orchestration: Combine agents and tasks into collaborative workflows
MCP Integration: Connect to external tools through Model Context Protocol

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK 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 Composio SDK

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

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

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

Step-by-step Guide

Step by step08 STEPS

Prerequisites

Before starting, make sure you have:

Python 3.9 or higher
A Composio account and API key
A Ignisign connection authorized in Composio
An OpenAI API key for the CrewAI LLM
Basic familiarity with Python

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
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

bash

pip install composio crewai crewai-tools[mcp] python-dotenv

What's happening:

composio connects your agent to Ignisign via MCP
crewai provides Agent, Task, Crew, and LLM primitives
crewai-tools[mcp] includes MCP helpers
python-dotenv loads environment variables from .env

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates with Composio
USER_ID scopes the session to your account
OPENAI_API_KEY lets CrewAI use your chosen OpenAI model

Import dependencies

python

import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

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

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")

What's happening:

CrewAI classes define agents and tasks, and run the workflow
MCPServerHTTP connects the agent to an MCP endpoint
Composio will give you a short lived Ignisign MCP URL

Create a Composio Tool Router session for Ignisign

python

composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["ignisign"])

url = session.mcp.url

What's happening:

You create a Ignisign only session through Composio
Composio returns an MCP HTTP URL that exposes Ignisign tools

Initialize the MCP Server

python

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )

What's Happening:

Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.

Create a CLI Chatloop and define the Crew

python

print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")

What's Happening:

Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

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

python

from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["ignisign"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Ignisign through Composio's Tool Router. The agent can perform Ignisign operations through natural language commands.

Next steps:

Add role-specific instructions to customize agent behavior
Plug in more toolkits for multi-app workflows
Chain tasks for complex multi-step operations

TOOLS

Supported Tools

Every Ignisign action and event your agent gets out of the box.

Ignisign API Authentication

Tool to authenticate an application over Ignisign API and retrieve a JWT.

Cancel Signature Request

Cancel (close) a signature request to terminate it.

Initialize Document

Tool to initialize a document for a signature request.

Create Signer

Tool to create a new signer.

Create Webhook Endpoint

Tool to create a new webhook endpoint for an application.

Delete Document

Tool to delete a specific document by its ID.

Delete Ignisign Signature Request

Permanently deletes a signature request from Ignisign by its ID.

Delete Signer

Tool to revoke/delete a signer from an Ignisign application environment.

Delete Webhook Endpoint

Delete a webhook endpoint by its ID.

Get application context

Tool to retrieve the global context of an application.

Get Document Information

Tool to retrieve document metadata by ID.

Get Missing Signer Inputs

Tool to determine missing inputs needed for a signer in a specific signature profile.

Get Signature Request Details

Tool to retrieve detailed information for a specific signature request.

Get Signature Request Document

Tool to retrieve the document associated with a specific signature request.

Get Signature Requests

Retrieves a paginated list of signature requests for a specific Ignisign application and environment.

Get Signed Document

Tool to download the signed document (signature proof) for a signature request.

Get Signer Input Constraints

Tool to get signer input constraints.

Get Signer Inputs

Retrieves the inputs provided by a specific signer for a signature request.

Get Signer Profile

Retrieve detailed information about a specific signer profile by its ID.

Get Signer Profiles

Retrieve all signer profiles for a specific Ignisign application environment.

Get Webhooks

Retrieves all webhook endpoints configured for a specific Ignisign application environment.

Initialize Ignisign Signature Request

Initialize a new signature request in Ignisign.

List Documents

Tool to retrieve documents linked to a signature request.

Provide Document Content Data JSON

Provides JSON content to an existing document in Ignisign.

Provide Document Content File

Tool to provide file content for a document.

Provide Document Content Private File

Provides private document content by submitting its SHA-256 hash to IgniSign.

Publish Signature Request

Tool to publish a draft signature request.

Search Signers

Tool to search for signers within an application environment with pagination support.

Update Document Information

Tool to update document metadata.

Update Signature Request

Tool to partially update a signature request in DRAFT state.

Update Signer

Updates an existing signer's profile assignment.

Update Webhook Endpoint

Tool to update an existing webhook endpoint.

FRAMEWORKS

How to build Ignisign MCP Agent with another framework

OpenAI Agents SDK

Use Ignisign MCP with OpenAI Agents SDK

Claude Agent SDK

Use Ignisign MCP with Claude Agent SDK

Claude Code

Use Ignisign MCP with Claude Code

Claude Cowork

Use Ignisign MCP with Claude Cowork

Codex

Use Ignisign MCP with Codex

OpenClaw

Use Ignisign MCP with OpenClaw

Hermes

Use Ignisign MCP with Hermes

CLI

Use Ignisign MCP with CLI

Google ADK

Use Ignisign MCP with Google ADK

LangChain

Use Ignisign MCP with LangChain

Vercel AI SDK

Use Ignisign MCP with Vercel AI SDK

Mastra AI

Use Ignisign MCP with Mastra AI

LlamaIndex

Use Ignisign MCP with LlamaIndex

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Google Drive

Oauth2

Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.

Google Docs

Oauth2

Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.

Google Super

Oauth2Api Key

Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.

Affinda

Api Key

Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data.

FAQ

Frequently asked questions

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.

Yes, you can. CrewAI 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.

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.

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.

Start with Ignisign.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Ignisign tool your agent needs.Free to start.

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Ignisign MCP with CrewAI

Connect Ignisign without auth hassles

Introduction

Also integrate Ignisign with

TL;DR

What is CrewAI?

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

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Composio Tool Router session for Ignisign

Initialize the MCP Server

Create a CLI Chatloop and define the Crew

Complete Code

Conclusion

Supported Tools

How to build Ignisign MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

Explore Other Toolkits

Google Drive

Google Docs

Google Super

Affinda

Frequently asked questions

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

Can I use Tool Router MCP with CrewAI?+

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

How safe is my data with Composio Tool Router?+

Start with Ignisign.It takes 30 seconds.

Teams ship real agents on Composio