# How to integrate Docmosis MCP with Google ADK ```json { "title": "How to integrate Docmosis MCP with Google ADK", "toolkit": "Docmosis", "toolkit_slug": "docmosis", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/docmosis/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/docmosis/framework/google-adk.md", "updated_at": "2026-05-12T10:09:06.847Z" } ``` ## Introduction This guide walks you through connecting Docmosis to Google ADK using the Composio tool router. By the end, you'll have a working Docmosis agent that can generate monthly invoice pdf for a customer, create personalized offer letters for new hires, produce event registration forms as word docs through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Docmosis account through Composio's Docmosis MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Docmosis with - [OpenAI Agents SDK](https://composio.dev/toolkits/docmosis/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/docmosis/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/docmosis/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/docmosis/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/docmosis/framework/codex) - [OpenClaw](https://composio.dev/toolkits/docmosis/framework/openclaw) - [Hermes](https://composio.dev/toolkits/docmosis/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/docmosis/framework/cli) - [LangChain](https://composio.dev/toolkits/docmosis/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/docmosis/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/docmosis/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/docmosis/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/docmosis/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get a Docmosis account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Docmosis - Build an agent that connects to Docmosis through MCP - Interact with Docmosis 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 Docmosis MCP server, and what's possible with it? The Docmosis MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Docmosis account. It provides structured and secure access to your document templates and generation capabilities, so your agent can perform actions like generating documents, merging data fields, exporting PDFs or Word files, and automating report creation on your behalf. - Dynamic document generation: Instantly create PDF or Word documents from pre-built templates by merging in your custom data fields. - Automated report and invoice creation: Let your agent assemble business reports, invoices, or letters using real-time input and reusable templates. - Template management and selection: Retrieve, list, and select from available templates for different document types or business needs. - Batch document processing: Generate multiple documents at once by feeding bulk data sets—perfect for automating repetitive paperwork. - Flexible file export and delivery: Export generated documents in your preferred format and deliver them to specified locations, systems, or users automatically. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `DOCMOSIS_DELETE_IMAGE` | Docmosis: Delete Image(s) | Tool to delete one or more stored images. Use when you need to remove images; ensure imageName(s) are valid before use. | | `DOCMOSIS_DELETE_TEMPLATE` | Docmosis: Delete Template(s) | Tool to delete one or more templates from the environment. Use when you need to remove templates; multiple templates can be deleted in a single request. | | `DOCMOSIS_ENVIRONMENT_READY` | Docmosis Environment Ready | Tool to verify environment readiness. Use when ensuring the environment is active and within quota before rendering documents. | | `DOCMOSIS_ENVIRONMENT_SUMMARY` | Docmosis Environment Summary | Tool to retrieve environment summary. Use when you need status, plan, and quota details of your Docmosis environment after authentication. | | `DOCMOSIS_GET_API_KEY` | Docmosis: Get API Key | Tool to extract the Docmosis API access key from connection metadata. Use before other Docmosis API calls to retrieve the Bearer token from the Authorization header. | | `DOCMOSIS_GET_BATCH_UPLOAD_STATUS` | Get Batch Upload Status | Tool to check the status of a template batch upload job. Use when monitoring batch upload progress or checking if a batch upload has completed. | | `DOCMOSIS_GET_IMAGE` | Download Docmosis Images | Tool to download one or more images. Use when you need to retrieve stored image files by name. If multiple names provided, images are returned in a zip archive. | | `DOCMOSIS_GET_RENDER_QUEUE` | Get Docmosis Render Queue | Tool to get current render queue status and utilization. Use when monitoring queue capacity before scheduling rendering tasks. | | `DOCMOSIS_GET_RENDER_TAGS` | Get Render Tags | Tool to retrieve statistics on renders tagged with user-defined phrases. Returns page counts and document counts aggregated monthly. Use when reporting activity of user groups or features. | | `DOCMOSIS_GET_SAMPLE_DATA` | Get Template Sample Data | Tool to generate sample data for a Docmosis template based on its structure. Creates placeholder values that can be used for testing renders. Returns data in JSON or XML format. | | `DOCMOSIS_GET_TEMPLATE` | Download Docmosis Templates | Tool to retrieve originally uploaded templates. Use when you need to download template files by name. If multiple names provided (up to 100), templates are returned in a zip archive. | | `DOCMOSIS_GET_TEMPLATE_DETAILS` | Get Docmosis Template Details | Tool to retrieve metadata for an uploaded template. Returns name, size, MD5 hash, last modified date, and error status. Use after uploading a template to verify it was stored correctly or to check if it has errors. | | `DOCMOSIS_GET_TEMPLATE_STRUCTURE` | Get Docmosis Template Structure | Tool to retrieve a template's parsed structure: fields, repeats, conditions, images, and refs. Use after uploading a template to inspect its JSON structure. | | `DOCMOSIS_LIST_IMAGES` | Docmosis: List Images | Tool to list available stock images. Use when you need to retrieve image names optionally filtered by folder. | | `DOCMOSIS_LIST_TEMPLATES` | Docmosis: List Templates | Tool to list all templates available in the environment. Use when you need to retrieve template names, optionally filtered by folder with pagination support. | | `DOCMOSIS_PING` | Docmosis Ping | Tool to check connectivity to Docmosis Cloud services. Use when validating that the service endpoint is reachable before other operations. | | `DOCMOSIS_PING_DOCMOSIS_SERVICE` | Ping Docmosis Service | Tool to check that Docmosis Cloud services are online and at least one server is listening. Use for diagnostics and monitoring to verify service availability. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Docmosis MCP server is an implementation of the Model Context Protocol that connects your AI agent to Docmosis. It provides structured and secure access so your agent can perform Docmosis 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 Docmosis 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=["docmosis"], ) 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 Docmosis 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=["docmosis"], ) 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 Docmosis operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Docmosis with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Docmosis using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Docmosis 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 Docmosis MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/docmosis/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/docmosis/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/docmosis/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/docmosis/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/docmosis/framework/codex) - [OpenClaw](https://composio.dev/toolkits/docmosis/framework/openclaw) - [Hermes](https://composio.dev/toolkits/docmosis/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/docmosis/framework/cli) - [LangChain](https://composio.dev/toolkits/docmosis/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/docmosis/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/docmosis/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/docmosis/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/docmosis/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 Docmosis MCP? With a standalone Docmosis MCP server, the agents and LLMs can only access a fixed set of Docmosis tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Docmosis 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 Docmosis tools. ### Can I manage the permissions and scopes for Docmosis while using Tool Router? Yes, absolutely. You can configure which Docmosis 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 Docmosis data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)