# How to integrate Parseur MCP with Claude Code ```json { "title": "How to integrate Parseur MCP with Claude Code", "toolkit": "Parseur", "toolkit_slug": "parseur", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/parseur/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/parseur/framework/claude-code.md", "updated_at": "2026-05-12T10:21:25.959Z" } ``` ## Introduction Manage your Parseur 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 Parseur with - [OpenAI Agents SDK](https://composio.dev/toolkits/parseur/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/parseur/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/parseur/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/parseur/framework/codex) - [OpenClaw](https://composio.dev/toolkits/parseur/framework/openclaw) - [Hermes](https://composio.dev/toolkits/parseur/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/parseur/framework/cli) - [Google ADK](https://composio.dev/toolkits/parseur/framework/google-adk) - [LangChain](https://composio.dev/toolkits/parseur/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/parseur/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/parseur/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/parseur/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/parseur/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 Parseur to Claude Code ### Connecting Parseur 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 Parseur MCP server, and what's possible with it? The Parseur MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Parseur account. It provides structured and secure access to your Parseur data extraction workflows, so your agent can perform actions like managing mailboxes, handling documents, configuring webhooks, and automating template operations on your behalf. - Mailbox management and discovery: Let your agent list, browse, and filter all Parseur mailboxes to keep tabs on your parsing operations and document streams. - Document listing and retrieval: Effortlessly fetch documents from specific mailboxes, enabling automated sorting, searching, or pagination of your parsed files. - Template and parsing rule automation: Ask your agent to list templates within any mailbox, so you can quickly inspect or update parsing rules as your data extraction needs evolve. - Webhook configuration and control: Enable your agent to create, update, pause, enable, or delete webhooks, making it easy to automate real-time data delivery to your other systems. - Comprehensive webhook inspection: Retrieve detailed webhook information or list all webhooks for a mailbox, ensuring you always know how and where your parsed data is flowing. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `PARSEUR_COPY_DOCUMENT` | Copy Document | Tool to copy a document to another mailbox. Use when you need to duplicate a document from one mailbox to another mailbox within Parseur. | | `PARSEUR_COPY_MAILBOX` | Copy Mailbox | Tool to copy a mailbox (parser) in Parseur. Creates a duplicate of the mailbox with all its configuration. Use when you need to duplicate an existing parser setup. | | `PARSEUR_CREATE_CUSTOM_DOWNLOAD` | Create custom download | Tool to create a custom download (export configuration) for a mailbox. Use when you need to define which fields should be exported to CSV or XLS format. | | `PARSEUR_CREATE_MAILBOX` | Create mailbox | Tool to create a new mailbox (parser) in Parseur. Use when you need to set up a new parser for document parsing with custom configuration. | | `PARSEUR_DELETE_CUSTOM_DOWNLOAD` | Delete custom download | Tool to delete a custom download (export configuration) from a mailbox. Use when permanently removing an export configuration after confirming its ID. | | `PARSEUR_DELETE_DOCUMENT` | Delete document | Tool to delete a specific document by ID. Use when permanently removing a document after confirming its ID. | | `PARSEUR_DELETE_MAILBOX` | Delete mailbox | Tool to delete a mailbox (parser) by ID. Use when permanently removing a mailbox after confirming its ID. | | `PARSEUR_DELETE_WEBHOOK` | Delete webhook | Tool to delete a specific webhook. Use when permanently removing a webhook after confirming its ID. | | `PARSEUR_DISABLE_WEBHOOK` | Disable webhook | Tool to disable a webhook for a mailbox. Removes the webhook association from the specified mailbox. Use when you need to stop an active webhook from sending parsed data. | | `PARSEUR_ENABLE_WEBHOOK` | Enable webhook | Enables a paused webhook for a specified mailbox, allowing it to receive and forward parsed document events. Use this action to re-enable a webhook that was previously paused. Only webhooks listed in 'available_webhook_set' (paused webhooks) can be enabled. After enabling, the webhook will appear in 'webhook_set' (active webhooks) and begin sending HTTP POST requests to its target URL when the configured event occurs (e.g., document.processed). | | `PARSEUR_GET_BOOTSTRAP_CONFIG` | Get Bootstrap Config | Tool to retrieve bootstrap configuration data. Use when you need system-wide configuration choices, field format mappings, maximum field lengths, or master parser definitions. | | `PARSEUR_GET_DOCUMENT` | Get Document | Tool to retrieve full details of a specific document by ID. Returns document status, processing info, parsed results, and download URLs for JSON, CSV, and XLS formats. | | `PARSEUR_GET_DOCUMENT_LOGS` | Get Document Logs | Tool to get document logs for a specific document. Returns paginated list of logs with status, source, and message details. Use when you need to troubleshoot or audit document processing history. | | `PARSEUR_GET_MAILBOX` | Get Mailbox by ID | Tool to retrieve full mailbox (parser) configuration by ID. Use when you need complete details about a specific mailbox including fields, webhooks, and settings. | | `PARSEUR_GET_MAILBOX_SCHEMA` | Get Mailbox Schema | Tool to retrieve the JSON schema for a mailbox's parsed fields. Use when you need to understand the structure and types of data fields extracted by a specific parser. | | `PARSEUR_LIST_CUSTOM_DOWNLOADS` | List Custom Downloads | Tool to retrieve custom downloads (export configurations) for a mailbox. Use when you need to list available export formats and their download URLs. | | `PARSEUR_LIST_DOCUMENTS_IN_MAILBOX` | List Documents in Mailbox | Tool to list documents within a specific mailbox. Use when you need to paginate, search, or sort the documents of a given mailbox after obtaining its ID. | | `PARSEUR_LIST_MAILBOXES2` | List Mailboxes (Full Details) | Tool to list mailboxes (parsers) with full configuration details. Returns paginated list of all mailboxes with document counts, processing statistics, and complete configuration settings. Use when you need comprehensive mailbox information including field configurations, processing options, and webhook settings. | | `PARSEUR_LIST_TEMPLATES` | List Templates for Mailbox | Tool to list all templates in a given mailbox. Use after fetching mailbox details when you need to page through and inspect available templates for further actions. | | `PARSEUR_REPROCESS_DOCUMENT` | Reprocess a document | Tool to reprocess a document. Triggers re-parsing of the document with the current template configuration. Use when you need to re-parse a document after template updates or to retry failed parsing. | | `PARSEUR_RETRIEVE_WEBHOOK` | Retrieve a webhook | Tool to retrieve details of a specific webhook. Use after creating or listing webhooks. | | `PARSEUR_SKIP_DOCUMENT` | Skip a document | Tool to skip a document. Marks the document as skipped and returns the updated document with status 'SKIPPED'. | | `PARSEUR_UPDATE_CUSTOM_DOWNLOAD` | Update custom download | Tool to update a custom download (export configuration) for a mailbox. Use when you need to modify the field list, name, or export settings for an existing download configuration. | | `PARSEUR_UPDATE_MAILBOX` | Update Mailbox | Tool to update a mailbox (parser) configuration. Use when you need to modify mailbox settings such as name, AI engine, processing options, or document handling rules. | | `PARSEUR_UPDATE_WEBHOOK` | Update webhook | Tool to update an existing webhook’s settings. Use when you need to change the webhook’s target URL, event type, headers, or name after creation. | | `PARSEUR_UPLOAD_EMAIL_DOCUMENT` | Upload Email Document | Tool to upload an email or text document to Parseur for parsing. Use when you need to programmatically send documents to a Parseur mailbox. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Parseur 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 Parseur account. It provides structured and secure access so Claude can perform Parseur 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 Parseur 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=["parseur"], ) 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 parseur-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: ['parseur'], }); 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 parseur-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 Parseur 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 (parseur-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 parseur-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 Parseur MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your parseur-composio entry in the list - This confirms that Claude Code can now access Parseur tools If everything is wired up, you should see your parseur-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Parseur The first time you try to use Parseur tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Parseur - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Parseur authorization flow - Return to the terminal and start using Parseur through Claude Code Once authenticated, you can ask Claude Code to perform Parseur operations in natural language. For example: - "List all documents in my invoices mailbox" - "Create a webhook to send parsed receipts" - "Pause the outgoing webhook for orders mailbox" ## 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=["parseur"], ) 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 parseur-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: ['parseur'], }); 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 parseur-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Parseur with Claude Code using Composio's MCP server. Now you can interact with Parseur directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Parseur 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 Parseur 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 Parseur MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/parseur/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/parseur/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/parseur/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/parseur/framework/codex) - [OpenClaw](https://composio.dev/toolkits/parseur/framework/openclaw) - [Hermes](https://composio.dev/toolkits/parseur/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/parseur/framework/cli) - [Google ADK](https://composio.dev/toolkits/parseur/framework/google-adk) - [LangChain](https://composio.dev/toolkits/parseur/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/parseur/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/parseur/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/parseur/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/parseur/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 Parseur MCP? With a standalone Parseur MCP server, the agents and LLMs can only access a fixed set of Parseur tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Parseur 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 Parseur tools. ### Can I manage the permissions and scopes for Parseur while using Tool Router? Yes, absolutely. You can configure which Parseur 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 Parseur data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)