# How to integrate Leiga MCP with Google ADK ```json { "title": "How to integrate Leiga MCP with Google ADK", "toolkit": "Leiga", "toolkit_slug": "leiga", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/leiga/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/leiga/framework/google-adk.md", "updated_at": "2026-05-12T10:17:20.469Z" } ``` ## Introduction This guide walks you through connecting Leiga to Google ADK using the Composio tool router. By the end, you'll have a working Leiga agent that can create a new project for q3 goals, assign tasks to marketing team members, update task status to completed for john through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Leiga account through Composio's Leiga MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Leiga with - [OpenAI Agents SDK](https://composio.dev/toolkits/leiga/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/leiga/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/leiga/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/leiga/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/leiga/framework/codex) - [OpenClaw](https://composio.dev/toolkits/leiga/framework/openclaw) - [Hermes](https://composio.dev/toolkits/leiga/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/leiga/framework/cli) - [LangChain](https://composio.dev/toolkits/leiga/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/leiga/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/leiga/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/leiga/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/leiga/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get a Leiga account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Leiga - Build an agent that connects to Leiga through MCP - Interact with Leiga 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 Leiga MCP server, and what's possible with it? The Leiga MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Leiga account. It provides structured and secure access to your project management workspace, so your agent can perform actions like creating tasks, updating project boards, automating workflows, assigning team members, and tracking progress on your behalf. - Automated task creation and assignment: Let your agent generate new project tasks and assign them to the right team members with deadlines and priorities. - Project board updates and management: Have your agent move tasks across workflow stages, update statuses, and keep project boards organized in real time. - Team collaboration enhancements: Enable your agent to post updates, add comments, and notify relevant teammates about project changes or deadlines. - Progress tracking and reporting: Ask your agent to summarize project statuses, highlight overdue items, and generate progress reports for stakeholders. - Workflow automation and reminders: Set up the agent to automate routine project workflows and send reminders for upcoming tasks or milestones. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `LEIGA_CREATE_PROJECT` | Create Project | Tool to create a new project in Leiga. Use after gathering project details and authenticating. | | `LEIGA_GET_FILE_LIST` | Get File List | Tool to retrieve a paginated list of files in a specified directory. Use after obtaining the directory ID to view files. | | `LEIGA_GET_ISSUE_DETAIL_BY_ISSUE_NUMBER` | Get Issue Detail by Number | Tool to fetch detailed information about a specific issue using its issue number. Use when you have an issue number and need complete issue details. | | `LEIGA_GET_ISSUE_SCHEMA` | Get Issue Schema | Tool to retrieve the issue custom-field schema. Use when you need the full list of field configurations after selecting an issue type. | | `LEIGA_GET_PROJECT_INFORMATION` | Get Project Information | Tool to fetch detailed information about a specific project by its ID. Use when you need complete project metadata, including owner and members. | | `LEIGA_GET_PROJECT_OVERVIEW_TEMPLATE` | Get Project Overview Template | Tool to retrieve the project overview template. Use when you need the structured overview template for a project after confirming its ID. | | `LEIGA_GET_PROJECT_TEMPLATE_LIST` | Get Project Template List | Tool to retrieve a list of project templates. Use when browsing available templates before creating a new project. | | `LEIGA_GET_VERSION_LIST` | Get Version List | Tool to fetch list of versions for a specific platform. Use when you need to view all available versions before deployment. | | `LEIGA_GET_WEBHOOK_TYPE_LIST` | Get Webhook Type List | Tool to retrieve the list of available webhook types. Use when configuring webhooks and you need to know valid event types. | | `LEIGA_LIST_PROJECTS` | List Projects | Tool to list all projects available to the authenticated user. Use when you need to retrieve your projects in paginated form (e.g., page 1 with 10 per page). | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Leiga MCP server is an implementation of the Model Context Protocol that connects your AI agent to Leiga. It provides structured and secure access so your agent can perform Leiga 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 Leiga 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=["leiga"], ) 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 Leiga 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=["leiga"], ) 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 Leiga operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Leiga with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Leiga using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Leiga 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 Leiga MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/leiga/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/leiga/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/leiga/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/leiga/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/leiga/framework/codex) - [OpenClaw](https://composio.dev/toolkits/leiga/framework/openclaw) - [Hermes](https://composio.dev/toolkits/leiga/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/leiga/framework/cli) - [LangChain](https://composio.dev/toolkits/leiga/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/leiga/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/leiga/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/leiga/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/leiga/framework/crew-ai) ## Related Toolkits - [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. - [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. - [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. - [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. - [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place. - [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives. - [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions. - [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date. - [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page. - [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes. - [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights. - [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Leiga MCP? With a standalone Leiga MCP server, the agents and LLMs can only access a fixed set of Leiga tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Leiga 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 Leiga tools. ### Can I manage the permissions and scopes for Leiga while using Tool Router? Yes, absolutely. You can configure which Leiga 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 Leiga data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)