# How to integrate Parseur MCP with Google ADK ```json { "title": "How to integrate Parseur MCP with Google ADK", "toolkit": "Parseur", "toolkit_slug": "parseur", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/parseur/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/parseur/framework/google-adk.md", "updated_at": "2026-05-12T10:21:25.959Z" } ``` ## Introduction This guide walks you through connecting Parseur to Google ADK 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 Google ADK 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) - [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 Here's what you'll learn: - Get a Parseur account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Parseur - Build an agent that connects to Parseur through MCP - Interact with Parseur using natural language ## What is Google ADK? Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol. Key features include: - Gemini Integration: Native support for Google's Gemini models - MCP Toolset: Built-in support for Model Context Protocol tools - Streamable HTTP: Connect to external services through streamable HTTP - CLI and Web UI: Run agents via command line or web interface ## 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 Before starting, make sure you have: - A Google API key for Gemini models - A Composio account and API key - Python 3.9 or later installed - Basic familiarity with Python ### 1. Getting API Keys for Google and Composio Google API Key - Go to [Google AI Studio](https://aistudio.google.com/app/apikey) and create an API key. - Copy the key and keep it safe. You will put this in GOOGLE_API_KEY. Composio API Key and User ID - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY. - Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID. ### 2. Install dependencies Inside your virtual environment, install the required packages. What's happening: - google-adk is Google's Agents Development Kit - composio connects your agent to Parseur via MCP - python-dotenv loads environment variables ```bash pip install google-adk composio python-dotenv ``` ### 3. Set up ADK project Set up a new Google ADK project. What's happening: - This creates an agent folder with a root agent file and .env file ```bash adk create my_agent ``` ### 4. Set environment variables Save all your credentials in the .env file. What's happening: - GOOGLE_API_KEY authenticates with Google's Gemini models - COMPOSIO_API_KEY authenticates with Composio - COMPOSIO_USER_ID identifies the user for session management ```bash GOOGLE_API_KEY=your-google-api-key COMPOSIO_API_KEY=your-composio-api-key COMPOSIO_USER_ID=your-user-id-or-email ``` ### 5. Import modules and validate environment What's happening: - os reads environment variables - Composio is the main Composio SDK client - GoogleProvider declares that you are using Google ADK as the agent runtime - Agent is the Google ADK LLM agent class - McpToolset lets the ADK agent call MCP tools over HTTP ```python import os import warnings from composio import Composio from dotenv import load_dotenv from google.adk.agents.llm_agent import Agent from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams from google.adk.tools.mcp_tool.mcp_toolset import McpToolset load_dotenv() warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*") GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") ``` ### 6. Create Composio client and Tool Router session What's happening: - Authenticates to Composio with your API key - Declares Google ADK as the provider - Spins up a short-lived MCP endpoint for your user and selected toolkit - Stores the MCP HTTP URL for the ADK MCP integration ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["parseur"], ) COMPOSIO_MCP_URL = composio_session.mcp.url, print(f"Composio MCP URL: {COMPOSIO_MCP_URL}") ``` ### 7. Set up the McpToolset and create the Agent What's happening: - Connects the ADK agent to the Composio MCP endpoint through McpToolset - Uses Gemini as the model powering the agent - Lists exact tool names in instruction to reduce misnamed tool calls ```python composio_toolset = McpToolset( connection_params=StreamableHTTPConnectionParams( url=COMPOSIO_MCP_URL, headers={"x-api-key": COMPOSIO_API_KEY} ) ) root_agent = Agent( model="gemini-2.5-flash", name="composio_agent", description="An agent that uses Composio tools to perform actions.", instruction=( "You are a helpful assistant connected to Composio. " "You have the following tools available: " "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, " "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. " "Use these tools to help users with Parseur operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ### 8. Run the agent Execute the agent from the project root. The web command opens a web portal where you can chat with the agent. What's happening: - adk run runs the agent in CLI mode - adk web . opens a web UI for interactive testing ```bash # Run in CLI mode adk run my_agent # Or run in web UI mode adk web ``` ## Complete Code ```python import os import warnings from composio import Composio from composio_google import GoogleProvider from dotenv import load_dotenv from google.adk.agents.llm_agent import Agent from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams from google.adk.tools.mcp_tool.mcp_toolset import McpToolset load_dotenv() warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*") GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider()) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["parseur"], ) COMPOSIO_MCP_URL = composio_session.mcp.url composio_toolset = McpToolset( connection_params=StreamableHTTPConnectionParams( url=COMPOSIO_MCP_URL, headers={"x-api-key": COMPOSIO_API_KEY} ) ) root_agent = Agent( model="gemini-2.5-flash", name="composio_agent", description="An agent that uses Composio tools to perform actions.", instruction=( "You are a helpful assistant connected to Composio. " "You have the following tools available: " "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, " "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. " "Use these tools to help users with Parseur operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Parseur with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Parseur using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Parseur tools - Environment variables keep your credentials secure and separate from code - Clear agent instructions reduce tool calling errors - The ADK web UI provides an interactive interface for testing and development You can extend this setup by adding more toolkits to the toolkits array in your session configuration. ## 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) - [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 Google ADK? Yes, you can. Google ADK 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)