How to connect Ignisign to Claude

Connect Claude Web, Desktop and Cowork to Ignisign MCP. Start a new signature request for a contract, add a new signer to this application, and more using natural language, with authentication handled for you.

Ignisign logoIgnisign
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

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Ignisign account to Claude via Composio Connect, enabling it to start a new signature request for a contract, add a new signer to this application, delete a completed document by its ID, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Ignisign with

Connecting Ignisign to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Ignisign account

Back in Claude, ask it to connect to Ignisign or give it any Ignisign-related task.

For example, ask Claude to:

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

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Ignisign account is ready to use.

What is the Ignisign Claude Connector, 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.

Troubleshooting

1. Why does Claude not use the Composio connector for Ignisign?

The connector can show as connected, but Claude must use it in each Ignisign conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Ignisign again.

2. Why does Claude show an MCP server error before Ignisign connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Ignisign.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Ignisign.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Ignisign authorization link not work?

The Composio connector is one server. Your Ignisign account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Ignisign connection.
  • Composio creates a fresh Ignisign authorization link.
  • Open that link in your browser and finish the Ignisign sign-in.

4. Why do Ignisign actions fail after they worked before?

The Ignisign connection can expire or lose permission.

  • Ask Claude to inspect the Ignisign connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Ignisign account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Ignisign.
  • If the action still fails with a permission error, check that the connected account has that permission in Ignisign itself.

5. How do I switch to a different Ignisign account?

Claude can manage the Ignisign connection for you.

  • Ask Claude to disconnect or delete the current Ignisign account.
  • Ask Claude to connect Ignisign again.
  • Open the new Composio authorization link for Ignisign.
  • Sign in with the other Ignisign account in the browser.
  • After the account connects, ask Claude to retry the Ignisign task.

6. Why is my Ignisign connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Ignisign connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click and click Clear cache.
  • If Ignisign tools still do not appear, click , disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Ignisign.
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.

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. Claude Cowork 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