# How to integrate Parseur MCP with LangChain ```json { "title": "How to integrate Parseur MCP with LangChain", "toolkit": "Parseur", "toolkit_slug": "parseur", "framework": "LangChain", "framework_slug": "langchain", "url": "https://composio.dev/toolkits/parseur/framework/langchain", "markdown_url": "https://composio.dev/toolkits/parseur/framework/langchain.md", "updated_at": "2026-05-12T10:21:25.959Z" } ``` ## Introduction This guide walks you through connecting Parseur to LangChain using the Composio tool router. By the end, you'll have a working Parseur agent that can list all documents in your invoices mailbox, create a webhook to send parsed receipts, pause the outgoing webhook for orders mailbox through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Parseur account through Composio's Parseur MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## 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 Code](https://composio.dev/toolkits/parseur/framework/claude-code) - [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) - [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 Here's what you'll learn: - Get and set up your OpenAI and Composio API keys - Connect your Parseur project to Composio - Create a Tool Router MCP session for Parseur - Initialize an MCP client and retrieve Parseur tools - Build a LangChain agent that can interact with Parseur - Set up an interactive chat interface for testing ## What is LangChain? LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context. Key features include: - Agent Framework: Build agents that can use tools and make decisions - MCP Integration: Connect to external services through Model Context Protocol adapters - Memory Management: Maintain conversation history across interactions - Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers ## 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 your AI agent to Parseur. It provides structured and secure access so your agent can perform Parseur operations on your behalf through a secure, permission-based interface. 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 No description provided. ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies No description provided. ```python pip install composio-langchain langchain-mcp-adapters langchain python-dotenv ``` ```typescript npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates your requests to Composio's API - COMPOSIO_USER_ID identifies the user for session management - OPENAI_API_KEY enables access to OpenAI's language models ```bash COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_composio_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import dependencies No description provided. ```python from langchain_mcp_adapters.client import MultiServerMCPClient from langchain.agents import create_agent from dotenv import load_dotenv from composio import Composio import asyncio import os load_dotenv() ``` ```typescript import { Composio } from '@composio/core'; import { LangchainProvider } from '@composio/langchain'; import { MultiServerMCPClient } from "@langchain/mcp-adapters"; import { createAgent } from "langchain"; import * as readline from 'readline'; import 'dotenv/config'; dotenv.config(); ``` ### 5. Initialize Composio client What's happening: - We're loading the COMPOSIO_API_KEY from environment variables and validating it exists - Creating a Composio instance that will manage our connection to Parseur tools - Validating that COMPOSIO_USER_ID is also set before proceeding ```python async def main(): composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) if not os.getenv("COMPOSIO_API_KEY"): raise ValueError("COMPOSIO_API_KEY is not set") if not os.getenv("COMPOSIO_USER_ID"): raise ValueError("COMPOSIO_USER_ID is not set") ``` ```typescript const composioApiKey = process.env.COMPOSIO_API_KEY; const userId = process.env.COMPOSIO_USER_ID; if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set'); if (!userId) throw new Error('COMPOSIO_USER_ID is not set'); async function main() { const composio = new Composio({ apiKey: composioApiKey as string, provider: new LangchainProvider() }); ``` ### 6. Create a Tool Router session What's happening: - We're creating a Tool Router session that gives your agent access to Parseur tools - The create method takes the user ID and specifies which toolkits should be available - The returned session.mcp.url is the MCP server URL that your agent will use - This approach allows the agent to dynamically load and use Parseur tools as needed ```python # Create Tool Router session for Parseur session = composio.create( user_id=os.getenv("COMPOSIO_USER_ID"), toolkits=['parseur'] ) url = session.mcp.url ``` ```typescript const session = await composio.create( userId as string, { toolkits: ['parseur'] } ); const url = session.mcp.url; ``` ### 7. Configure the agent with the MCP URL No description provided. ```python client = MultiServerMCPClient({ "parseur-agent": { "transport": "streamable_http", "url": session.mcp.url, "headers": { "x-api-key": os.getenv("COMPOSIO_API_KEY") } } }) tools = await client.get_tools() agent = create_agent("gpt-5", tools) ``` ```typescript const client = new MultiServerMCPClient({ "parseur-agent": { transport: "http", url: url, headers: { "x-api-key": process.env.COMPOSIO_API_KEY } } }); const tools = await client.getTools(); const agent = createAgent({ model: "gpt-5", tools }); ``` ### 8. Set up interactive chat interface No description provided. ```python conversation_history = [] print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Parseur related question or task to the agent.\n") while True: user_input = input("You: ").strip() if user_input.lower() in ['exit', 'quit', 'bye']: print("\nGoodbye!") break if not user_input: continue conversation_history.append({"role": "user", "content": user_input}) print("\nAgent is thinking...\n") response = await agent.ainvoke({"messages": conversation_history}) conversation_history = response['messages'] final_response = response['messages'][-1].content print(f"Agent: {final_response}\n") ``` ```typescript let conversationHistory: any[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log("Ask any Parseur related question or task to the agent.\n"); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: 'You: ' }); rl.prompt(); rl.on('line', async (userInput: string) => { const trimmedInput = userInput.trim(); if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } conversationHistory.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); const response = await agent.invoke({ messages: conversationHistory }); conversationHistory = response.messages; const finalResponse = response.messages[response.messages.length - 1]?.content; console.log(`Agent: ${finalResponse}\n`); rl.prompt(); }); rl.on('close', () => { console.log('\n👋 Session ended.'); process.exit(0); }); ``` ### 9. Run the application No description provided. ```python if __name__ == "__main__": asyncio.run(main()) ``` ```typescript main().catch((err) => { console.error('Fatal error:', err); process.exit(1); }); ``` ## Complete Code ```python from langchain_mcp_adapters.client import MultiServerMCPClient from langchain.agents import create_agent from dotenv import load_dotenv from composio import Composio import asyncio import os load_dotenv() async def main(): composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) if not os.getenv("COMPOSIO_API_KEY"): raise ValueError("COMPOSIO_API_KEY is not set") if not os.getenv("COMPOSIO_USER_ID"): raise ValueError("COMPOSIO_USER_ID is not set") session = composio.create( user_id=os.getenv("COMPOSIO_USER_ID"), toolkits=['parseur'] ) url = session.mcp.url client = MultiServerMCPClient({ "parseur-agent": { "transport": "streamable_http", "url": url, "headers": { "x-api-key": os.getenv("COMPOSIO_API_KEY") } } }) tools = await client.get_tools() agent = create_agent("gpt-5", tools) conversation_history = [] print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Parseur related question or task to the agent.\n") while True: user_input = input("You: ").strip() if user_input.lower() in ['exit', 'quit', 'bye']: print("\nGoodbye!") break if not user_input: continue conversation_history.append({"role": "user", "content": user_input}) print("\nAgent is thinking...\n") response = await agent.ainvoke({"messages": conversation_history}) conversation_history = response['messages'] final_response = response['messages'][-1].content print(f"Agent: {final_response}\n") if __name__ == "__main__": asyncio.run(main()) ``` ```typescript import { Composio } from '@composio/core'; import { LangchainProvider } from '@composio/langchain'; import { MultiServerMCPClient } from "@langchain/mcp-adapters"; import { createAgent } from "langchain"; import * as readline from 'readline'; import 'dotenv/config'; const composioApiKey = process.env.COMPOSIO_API_KEY; const userId = process.env.COMPOSIO_USER_ID; if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set'); if (!userId) throw new Error('COMPOSIO_USER_ID is not set'); async function main() { const composio = new Composio({ apiKey: composioApiKey as string, provider: new LangchainProvider() }); const session = await composio.create( userId as string, { toolkits: ['parseur'] } ); const url = session.mcp.url; const client = new MultiServerMCPClient({ "parseur-agent": { transport: "http", url: url, headers: { "x-api-key": process.env.COMPOSIO_API_KEY } } }); const tools = await client.getTools(); const agent = createAgent({ model: "gpt-5", tools }); let conversationHistory: any[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log("Ask any Parseur related question or task to the agent.\n"); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: 'You: ' }); rl.prompt(); rl.on('line', async (userInput: string) => { const trimmedInput = userInput.trim(); if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } conversationHistory.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); const response = await agent.invoke({ messages: conversationHistory }); conversationHistory = response.messages; const finalResponse = response.messages[response.messages.length - 1]?.content; console.log(`Agent: ${finalResponse}\n`); rl.prompt(); }); rl.on('close', () => { console.log('\nSession ended.'); process.exit(0); }); } main().catch((err) => { console.error('Fatal error:', err); process.exit(1); }); ``` ## Conclusion You've successfully built a LangChain agent that can interact with Parseur through Composio's Tool Router. Key features of this implementation: - Dynamic tool loading through Composio's Tool Router - Conversation history maintenance for context-aware responses - Async Python provides clean, efficient execution of agent workflows You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## 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 Code](https://composio.dev/toolkits/parseur/framework/claude-code) - [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) - [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 LangChain? Yes, you can. LangChain 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)