# How to integrate Ignisign MCP with Claude Code ```json { "title": "How to integrate Ignisign MCP with Claude Code", "toolkit": "Ignisign", "toolkit_slug": "ignisign", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/ignisign/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/ignisign/framework/claude-code.md", "updated_at": "2026-05-12T10:15:40.413Z" } ``` ## 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: - Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach - Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control ## 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 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) - [CLI](https://composio.dev/toolkits/ignisign/framework/cli) - [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) ## TL;DR - Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles. - Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling. - Handling Large tool responses out of LLM context to minimize context rot. - Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need. ## Connect Ignisign to Claude Code ### Connecting Ignisign to Claude Code using Composio 1. Add the Composio MCP to Claude ```bash claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp ``` ## What is Claude Code? Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working. Key features include: - Terminal-Native Experience: Work with Claude directly in your command line without switching contexts - MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities - Project Context: Claude understands your project structure and can read, write, and modify files - Interactive Development: Ask questions, debug code, and get help in real-time while coding - Multi-Platform: Works on macOS, Linux, WSL, and Windows ## 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. ## Creating MCP Server - Stand-alone vs Composio SDK The Ignisign MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Ignisign account. It provides structured and secure access so Claude can perform Ignisign operations on your behalf. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. 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 ### 1. Install Claude Code To install Claude Code, use one of the following methods based on your operating system: ```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 ``` ### 2. Set up Claude Code 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 ```bash cd your-project-folder claude ``` ### 3. Set up environment variables Create a .env file in your project root with the following variables: - COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code)) - USER_ID identifies the user for session management (use any unique identifier) ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ``` ### 4. Install Composio library No description provided. ```python pip install composio-core python-dotenv ``` ```typescript npm install @composio/core dotenv ``` ### 5. Generate Composio MCP URL No description provided. ```python 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}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['ignisign'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http ignisign-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ### 6. Run the script and copy the MCP URL No description provided. ```python python generate_mcp_url.py ``` ```typescript node --loader ts-node/esm generate_mcp_url.ts # or if using tsx tsx generate_mcp_url.ts ``` ### 7. Add Ignisign MCP to Claude Code 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. ```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 ``` ### 8. Verify the installation 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: ```bash claude mcp list ``` ### 9. 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 ```python 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}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['ignisign'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http ignisign-composio "${composioMcpUrl}" --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](https://composio.dev/toolkits/ignisign/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/ignisign/framework/claude-agents-sdk) - [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) - [CLI](https://composio.dev/toolkits/ignisign/framework/cli) - [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) ## 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. - [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. - [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. - [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. - [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. - [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. - [Cloudpress](https://composio.dev/toolkits/cloudpress) - Cloudpress is a content export tool for Google Docs and Notion. It automates publishing to your favorite Content Management Systems. - [Contentful graphql](https://composio.dev/toolkits/contentful_graphql) - Contentful graphql is a content delivery API that lets you access Contentful data using GraphQL queries. It gives you efficient, flexible ways to fetch and manage structured content for any digital project. - [Conversion tools](https://composio.dev/toolkits/conversion_tools) - Conversion Tools is an online service for converting documents between formats such as PDF, Word, Excel, XML, and CSV. It lets you automate complex document workflows with just a few clicks. - [Convertapi](https://composio.dev/toolkits/convertapi) - ConvertAPI is a robust file conversion service for documents, images, and spreadsheets. It streamlines programmatic format changes and lets developers automate complex workflows with a single API. - [Craftmypdf](https://composio.dev/toolkits/craftmypdf) - CraftMyPDF is a web-based service for designing and generating PDFs with templates and live data. It streamlines document creation by automating personalized PDFs at scale. ## 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 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. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)