# How to integrate Docsautomator MCP with Google ADK ```json { "title": "How to integrate Docsautomator MCP with Google ADK", "toolkit": "Docsautomator", "toolkit_slug": "docsautomator", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/docsautomator/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/docsautomator/framework/google-adk.md", "updated_at": "2026-03-29T06:30:49.122Z" } ``` ## Introduction This guide walks you through connecting Docsautomator to Google ADK using the Composio tool router. By the end, you'll have a working Docsautomator agent that can generate an invoice from the 'invoice' template, create onboarding document for new employee, list all docsautomator templates available to me through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Docsautomator account through Composio's Docsautomator MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Docsautomator with - [OpenAI Agents SDK](https://composio.dev/toolkits/docsautomator/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/docsautomator/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/docsautomator/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/docsautomator/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/docsautomator/framework/codex) - [OpenClaw](https://composio.dev/toolkits/docsautomator/framework/openclaw) - [Hermes](https://composio.dev/toolkits/docsautomator/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/docsautomator/framework/cli) - [LangChain](https://composio.dev/toolkits/docsautomator/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/docsautomator/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/docsautomator/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/docsautomator/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/docsautomator/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get a Docsautomator account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Docsautomator - Build an agent that connects to Docsautomator through MCP - Interact with Docsautomator 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 Docsautomator MCP server, and what's possible with it? The Docsautomator MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Docsautomator account. It provides structured and secure access so your agent can perform Docsautomator operations on your behalf. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `DOCSAUTOMATOR_CREATE_AUTOMATION` | Create Automation | Tool to create a new DocsAutomator automation with specified data source and optional Google Doc template. Use when you need to set up a new document automation workflow. PDF templates must be uploaded through the DocsAutomator app interface. | | `DOCSAUTOMATOR_DELETE_AUTOMATION` | Delete Automation | Tool to permanently delete an automation and all associated data. Use when you need to remove an automation that is no longer needed. This action cannot be undone. | | `DOCSAUTOMATOR_DUPLICATE_AUTOMATION` | Duplicate Automation | Tool to create a copy of an existing automation with ' COPY' appended to the title. Use when you need to duplicate an existing automation without recreating it from scratch. | | `DOCSAUTOMATOR_GET_AUTOMATION` | Get Automation Details | Tool to retrieve details of a specific automation by its ID. Use when you need to fetch configuration, data source settings, and template information for an automation. | | `DOCSAUTOMATOR_GET_QUEUE_STATISTICS` | Get Queue Statistics | Tool to retrieve current document generation queue statistics for your workspace. Use when monitoring queue health or checking processing capacity. | | `DOCSAUTOMATOR_LIST_AUTOMATIONS` | List Automations | Tool to retrieve all automations in your workspace with their basic details. Use when you need to view, list, or enumerate existing automations. | | `DOCSAUTOMATOR_LIST_SIGNING_SESSIONS` | List Signing Sessions | Tool to retrieve signing sessions with optional filtering by status or signer email. Returns paginated results. Use when you need to list or search for signing sessions in DocsAutomator. | | `DOCSAUTOMATOR_SEND_TEST_EMAIL` | Send Test Email | Tool to send a test email with a sample PDF attachment to verify email configuration. Use when you need to test email delivery for a specific automation. Rate limited to 25 emails per hour per automation. | | `DOCSAUTOMATOR_UPDATE_AUTOMATION` | Update Automation | Tool to update an existing automation's settings in DocsAutomator. Only the fields included in the request are updated. Use when you need to modify automation properties like title, template link, locale settings, or activation status. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Docsautomator MCP server is an implementation of the Model Context Protocol that connects your AI agent to Docsautomator. It provides structured and secure access so your agent can perform Docsautomator 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 Docsautomator 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=["docsautomator"], ) 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 Docsautomator 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=["docsautomator"], ) 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 Docsautomator operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Docsautomator with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Docsautomator using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Docsautomator 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 Docsautomator MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/docsautomator/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/docsautomator/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/docsautomator/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/docsautomator/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/docsautomator/framework/codex) - [OpenClaw](https://composio.dev/toolkits/docsautomator/framework/openclaw) - [Hermes](https://composio.dev/toolkits/docsautomator/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/docsautomator/framework/cli) - [LangChain](https://composio.dev/toolkits/docsautomator/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/docsautomator/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/docsautomator/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/docsautomator/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/docsautomator/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 Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly. - [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place. - [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations. - [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. - [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals. - [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem. - [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity. - [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently. - [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place. - [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [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. - [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place. - [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. - [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Docsautomator MCP? With a standalone Docsautomator MCP server, the agents and LLMs can only access a fixed set of Docsautomator tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Docsautomator 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 Docsautomator tools. ### Can I manage the permissions and scopes for Docsautomator while using Tool Router? Yes, absolutely. You can configure which Docsautomator 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 Docsautomator data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)