# How to integrate Ignisign MCP with Atomic Agent ```json { "title": "How to integrate Ignisign MCP with Atomic Agent", "toolkit": "Ignisign", "toolkit_slug": "ignisign", "framework": "Atomic Agent", "framework_slug": "atomic-agent", "url": "https://composio.dev/toolkits/ignisign/framework/atomic-agent", "markdown_url": "https://composio.dev/toolkits/ignisign/framework/atomic-agent.md", "updated_at": "2026-08-11T13:10:58.548Z" } ``` ## Introduction Atomic Agent is an open-source AI agent that runs on your machine and supports local models through llama.cpp. Connect it to 1,500+ apps through Composio, including Ignisign. This guide uses Atomic Agent's built-in Composio integration. You need Atomic Agent v0.5.6 or later, your own Composio API key, and a Ignisign account. See the [Atomic Agent documentation](https://atomicagent.io/docs/?cta_placement=atomic-agent-docs) for installation instructions. ## Also integrate Ignisign with - [OpenAI Agents SDK](https://composio.dev/toolkits/ignisign/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ignisign/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ignisign/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ignisign/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ignisign/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ignisign/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ignisign/framework/hermes-agent) - [Google ADK](https://composio.dev/toolkits/ignisign/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ignisign/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ignisign/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/ignisign/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/ignisign/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ignisign/framework/crew-ai) - [Pydantic AI](https://composio.dev/toolkits/ignisign/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/ignisign/framework/autogen) ## TL;DR ### How Atomic Agent connects to Ignisign Atomic Agent connects to Composio's Tool Router over Streamable HTTP MCP. It discovers the tools needed for your request, and Composio handles account authentication. Execution and account-connection tools follow Atomic Agent's configured approval policy. Review any approval prompt before allowing an action on your connected account. ## Connect Ignisign to Atomic Agent ### Connect Ignisign to Atomic Agent - Sign up or sign in to the [Composio dashboard](https://dashboard.composio.dev/?cta_placement=atomic-agent-api-key). Copy your API key. - In Atomic Agent, open the Integrations tab and select Composio. Select API key, press e, paste the key, and press Enter. The tools become available immediately, without a restart. - Ask Atomic Agent to do something in Ignisign. It searches Composio for the right tool. - On first use, open the sign-in link returned in the chat. Connect your Ignisign account, then return to Atomic Agent to continue. ### Headless setup Add the following line to ~/.atomic-agent/.env, replacing YOUR_COMPOSIO_API_KEY with your key. Start Atomic Agent after saving the file. ```bash COMPOSIO_API_KEY=YOUR_COMPOSIO_API_KEY ``` ## 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 | Tool slug | Name | Description | |---|---|---| | `IGNISIGN_API_AUTHENTICATION` | Ignisign API Authentication | Tool to authenticate an application over Ignisign API and retrieve a JWT. Use when obtaining a bearer token before making other API calls. | | `IGNISIGN_CANCEL_SIGNATURE_REQUEST` | Cancel Signature Request | Cancel (close) a signature request to terminate it. This uses the Ignisign /close endpoint which permanently cancels the signature workflow. Use this when you need to abort a signature request that is in DRAFT or IN_PROGRESS status. This operation is idempotent - calling it on an already cancelled request returns success without error. | | `IGNISIGN_CREATE_DOCUMENT` | Initialize Document | Tool to initialize a document for a signature request. Use when linking a new document to an existing signature request after creating that request. | | `IGNISIGN_CREATE_SIGNER` | Create Signer | Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile. | | `IGNISIGN_CREATE_WEBHOOK_ENDPOINT` | Create Webhook Endpoint | Tool to create a new webhook endpoint for an application. Use after obtaining application ID and environment to register for event notifications. | | `IGNISIGN_DELETE_DOCUMENT` | Delete Document | Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete. | | `IGNISIGN_DELETE_SIGNATURE_REQUEST` | Delete Ignisign Signature Request | Permanently deletes a signature request from Ignisign by its ID. This action is irreversible and removes the signature request along with all associated data. The signature request ID can be obtained from the IGNISIGN_INIT_SIGNATURE_REQUEST action or IGNISIGN_GET_SIGNATURE_REQUESTS action. | | `IGNISIGN_DELETE_SIGNER` | Delete Signer | Tool to revoke/delete a signer from an Ignisign application environment. This action permanently revokes the signer's access and is idempotent (can be called multiple times on the same signer). Use when you need to remove a signer after confirming their signer ID. | | `IGNISIGN_DELETE_WEBHOOK_ENDPOINT` | Delete Webhook Endpoint | Delete a webhook endpoint by its ID. After deletion, returns the list of remaining webhook endpoints configured for the application environment. Use this tool when you need to remove a webhook that is no longer needed or to clean up unused webhooks. The webhook ID can be obtained from the create webhook or list webhooks endpoints. | | `IGNISIGN_GET_APPLICATION_CONTEXT` | Get application context | Tool to retrieve the global context of an application. Use when you need configuration and environment settings for a given app. | | `IGNISIGN_GET_DOCUMENT_INFORMATION` | Get Document Information | Tool to retrieve document metadata by ID. Use when you need detailed information of a specific document after obtaining its ID. | | `IGNISIGN_GET_MISSING_SIGNER_INPUTS` | Get Missing Signer Inputs | Tool to determine missing inputs needed for a signer in a specific signature profile. Use after selecting a signature profile and signer to identify required fields. | | `IGNISIGN_GET_SIGNATURE_REQUEST_DETAILS` | Get Signature Request Details | Tool to retrieve detailed information for a specific signature request. Use after creating or listing a signature request to inspect its details. | | `IGNISIGN_GET_SIGNATURE_REQUEST_DOCUMENT` | Get Signature Request Document | Tool to retrieve the document associated with a specific signature request. The action downloads the original file of a document. Provide `documentId` to select a specific document or omit to use the first available document of the request. | | `IGNISIGN_GET_SIGNATURE_REQUESTS` | Get Signature Requests | Retrieves a paginated list of signature requests for a specific Ignisign application and environment. Use this to list all signature requests (drafts, in-progress, completed, cancelled) in an application. Each signature request can have associated documents and signers. Returns pagination metadata to iterate through large result sets. Note: The app_env parameter must match your API key's environment scope. | | `IGNISIGN_GET_SIGNED_DOCUMENT` | Get Signed Document | Tool to download the signed document (signature proof) for a signature request. The action will: 1) Resolve the first documentId from the signature request details. 2) Try v4: GET /documents/{documentId}/signatures/PDF_WITH_SIGNATURES 3) Fallback v3: GET /v3/documents/{documentId}/signature-proof 4) Final fallback: GET /documents/{documentId}/file (original file) | | `IGNISIGN_GET_SIGNER_INPUT_CONSTRAINTS` | Get Signer Input Constraints | Tool to get signer input constraints. Use when you need to know which fields are required from signers for a given signer profile. | | `IGNISIGN_GET_SIGNER_INPUTS` | Get Signer Inputs | Retrieves the inputs provided by a specific signer for a signature request. Returns field values the signer has submitted (e.g., firstName, lastName, email). Use this after a signer has been added to a signature request to fetch their profile information. The signer must be associated with the specified signature request. | | `IGNISIGN_GET_SIGNER_PROFILE` | Get Signer Profile | Retrieve detailed information about a specific signer profile by its ID. Use this to get profile settings including integration mode, authentication methods, and associated signers. First use 'Get Signer Profiles' to list available profile IDs. | | `IGNISIGN_GET_SIGNER_PROFILES` | Get Signer Profiles | Retrieve all signer profiles for a specific Ignisign application environment. Use this tool to list all configured signer profiles that define how signers interact with signature requests. Each profile specifies integration mode (BY_SIDE, EMBEDDED, or MACHINE_TO_MACHINE), authentication methods, and other settings. Returns profile IDs which can be used when creating signers or signature requests. | | `IGNISIGN_GET_WEBHOOKS` | Get Webhooks | Retrieves all webhook endpoints configured for a specific Ignisign application environment. Returns the list of webhooks including their URLs, descriptions, and creation timestamps. Use this to audit existing webhook integrations or verify webhook configurations. | | `IGNISIGN_INIT_SIGNATURE_REQUEST` | Initialize Ignisign Signature Request | Initialize a new signature request in Ignisign. This is the first step in creating a signature workflow. After initialization, you can add documents (IGNISIGN_CREATE_DOCUMENT), assign signers (IGNISIGN_CREATE_SIGNER), and publish the request (IGNISIGN_PUBLISH_SIGNATURE_REQUEST) to start the signing process. | | `IGNISIGN_LIST_DOCUMENTS` | List Documents | Tool to retrieve documents linked to a signature request. The action works by calling the signature request context endpoint and extracting its documentIds, then fetching each document detail. | | `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_DATA_JSON` | Provide Document Content Data JSON | Provides JSON content to an existing document in Ignisign. Use this action after creating a document with IGNISIGN_CREATE_DOCUMENT to attach structured JSON data that will be associated with a signature request. The JSON content is stored and can be used for document generation or data binding in signature workflows. | | `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_FILE` | Provide Document Content File | Tool to provide file content for a document. Use after creating a document to attach its file content. | | `IGNISIGN_PROVIDE_DOCUMENT_CONTENT_PRIVATE_FILE` | Provide Document Content Private File | Provides private document content by submitting its SHA-256 hash to IgniSign. Use this after creating a document with IGNISIGN_CREATE_DOCUMENT when the document content should remain private (not uploaded). The hash proves document integrity without exposing its contents. The document status will change to 'PROVIDED' upon success. | | `IGNISIGN_PUBLISH_SIGNATURE_REQUEST` | Publish Signature Request | Tool to publish a draft signature request. Use after adding all documents and signer details to the draft. | | `IGNISIGN_SEARCH_SIGNERS` | Search Signers | Tool to search for signers within an application environment with pagination support. Use after obtaining application ID and environment. Requires a non-empty filter string to search by name, email, or external ID. Use '*' to match all signers. Supports page and pageSize parameters to paginate through large result sets. | | `IGNISIGN_UPDATE_DOCUMENT_INFORMATION` | Update Document Information | Tool to update document metadata. Use when you need to change a document's label, description, or external identifier after creation. | | `IGNISIGN_UPDATE_SIGNATURE_REQUEST` | Update Signature Request | Tool to partially update a signature request in DRAFT state. Use when you need to modify draft request metadata before sending. | | `IGNISIGN_UPDATE_SIGNER` | Update Signer | Updates an existing signer's profile assignment. Use this to change which signer profile a signer is associated with. The signer must already exist in the application environment. Requires: app_id (from Get Application Context), signer_id (from Create Signer or Search Signers), and signer_profile_id (from Get Signer Profiles). | | `IGNISIGN_UPDATE_WEBHOOK_ENDPOINT` | Update Webhook Endpoint | Tool to update an existing webhook endpoint. Use when you have a webhook ID and want to modify its destination URL or description. Example: Update the URL of webhook `68e7adc882353ea4e072bdbe` to `https://example.com/webhook`. | ## Supported Triggers None listed. ## Troubleshooting ### Why is my API key rejected? Copy the key directly from the Composio dashboard. Atomic Agent requires ASCII characters because it sends the key in an HTTP header. Remove any extra characters introduced when copying. ### Why are Composio tools unavailable after saving a key? Check that you use Atomic Agent v0.5.6 or later and that Composio is enabled in your configuration. A "composio": { "enabled": false } setting disables the integration while keeping the saved key on disk. ### Does Composio have a free plan? The Hobby plan includes 100,000 tool calls per month. Composio-managed OAuth apps have a lower included allowance. See [Composio pricing](/pricing) for the current limits that apply to your connection. ## Complete Code None listed. ## Conclusion ### Use Ignisign from Atomic Agent With your account connected, ask Atomic Agent to work with Ignisign in natural language. You can connect more apps through the same Composio integration as you need them. Visit the [Atomic Agent website](https://atomicagent.io/?cta_placement=atomic-agent-site) or inspect the [Atomic Agent source code](https://github.com/AtomicBot-ai/atomic-agent?cta_placement=atomic-agent-repo). ## How to build Ignisign MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/ignisign/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ignisign/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/ignisign/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/ignisign/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/ignisign/framework/codex) - [OpenClaw](https://composio.dev/toolkits/ignisign/framework/openclaw) - [Hermes](https://composio.dev/toolkits/ignisign/framework/hermes-agent) - [Google ADK](https://composio.dev/toolkits/ignisign/framework/google-adk) - [LangChain](https://composio.dev/toolkits/ignisign/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/ignisign/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/ignisign/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/ignisign/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/ignisign/framework/crew-ai) - [Pydantic AI](https://composio.dev/toolkits/ignisign/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/ignisign/framework/autogen) ## Related Toolkits - [Google Drive](https://composio.dev/toolkits/googledrive) - 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](https://composio.dev/toolkits/googledocs) - 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](https://composio.dev/toolkits/googlesuper) - 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. - [ActiveMerge](https://composio.dev/toolkits/active_merge) - ActiveMerge is a document automation platform for generating documents, images, merged files, and e-signature workflows. It helps teams turn templates and stored files into finished, shareable documents faster. - [Affinda](https://composio.dev/toolkits/affinda) - 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. - [Agility cms](https://composio.dev/toolkits/agility_cms) - Agility CMS is a headless content management system for building and managing digital experiences across platforms. It lets teams update content quickly and deliver omnichannel experiences with ease. - [Airparser](https://composio.dev/toolkits/airparser) - Airparser is an AI-powered parser for extracting structured data from emails, documents, PDFs, and files. It turns messy inbound content into clean fields your apps and workflows can use. - [Algodocs](https://composio.dev/toolkits/algodocs) - Algodocs is an AI-powered platform that automates data extraction from business documents. It delivers fast, secure, and accurate processing without templates or manual training. - [Api2pdf](https://composio.dev/toolkits/api2pdf) - Api2Pdf is a REST API for generating PDFs from HTML, URLs, and documents using powerful engines like wkhtmltopdf and Headless Chrome. It streamlines document conversion and automation for developers and businesses. - [Archive.org](https://composio.dev/toolkits/archive_org) - Archive.org is the Internet Archive's digital library of websites, books, audio, video, and images. Use it to preserve, explore, and access historical web captures and public-domain media. - [Aryn](https://composio.dev/toolkits/aryn) - Aryn is an AI-powered platform for parsing, extracting, and analyzing data from unstructured documents. Use it to automate document processing and unlock actionable insights from your files. - [Boldsign](https://composio.dev/toolkits/boldsign) - Boldsign is a digital eSignature platform for sending, signing, and tracking documents online. Organizations use it to automate agreements and manage legally binding workflows efficiently. - [Boloforms](https://composio.dev/toolkits/boloforms) - BoloForms is an eSignature platform built for small businesses, offering unlimited signatures, templates, and forms. It simplifies digital document signing and team collaboration at a predictable, fixed price. - [Box](https://composio.dev/toolkits/box) - Box is a cloud content management and file sharing platform for businesses. It helps teams securely store, organize, and collaborate on files from anywhere. - [Box MCP](https://composio.dev/toolkits/box_mcp) - Box MCP is Box's hosted MCP server that exposes enterprise files, folders, and metadata. It provides secure, centralized access to corporate content for search and management. - [Carbone](https://composio.dev/toolkits/carbone) - Carbone is a blazing-fast report generator that turns JSON data into PDFs, Word docs, spreadsheets, and more using flexible templates. It lets you automate document creation at scale with minimal code. - [Castingwords](https://composio.dev/toolkits/castingwords) - CastingWords is a transcription service specializing in human-powered, accurate transcripts via a simple API. Get seamless audio-to-text conversion for interviews, meetings, podcasts, and more. - [CertSeal](https://composio.dev/toolkits/cert_seal) - CertSeal is an API platform for issuing and managing verifiable digital certificates. Use it to automate trusted certificate workflows for recipients, batches, designs, and webhooks. - [Cloudconvert](https://composio.dev/toolkits/cloudconvert) - CloudConvert is a powerful file conversion service supporting over 200 file formats. It streamlines converting, compressing, and managing documents, media, and more, all in one place. - [Cloudlayer](https://composio.dev/toolkits/cloudlayer) - Cloudlayer is a document and asset generation service for creating PDFs and images via API or SDKs. It lets you automate high-quality doc creation, saving dev time and reducing manual work. ## Frequently Asked Questions ### 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 Atomic Agent? Yes, you can. Atomic Agent 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. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)