# How to integrate Appcircle MCP with Google ADK ```json { "title": "How to integrate Appcircle MCP with Google ADK", "toolkit": "Appcircle", "toolkit_slug": "appcircle", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/appcircle/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/appcircle/framework/google-adk.md", "updated_at": "2026-05-12T10:01:45.854Z" } ``` ## Introduction This guide walks you through connecting Appcircle to Google ADK using the Composio tool router. By the end, you'll have a working Appcircle agent that can trigger a new ios app build pipeline, fetch latest build status for your project, list all available distribution profiles through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Appcircle account through Composio's Appcircle MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Appcircle with - [OpenAI Agents SDK](https://composio.dev/toolkits/appcircle/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/appcircle/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/appcircle/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/appcircle/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/appcircle/framework/codex) - [OpenClaw](https://composio.dev/toolkits/appcircle/framework/openclaw) - [Hermes](https://composio.dev/toolkits/appcircle/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/appcircle/framework/cli) - [LangChain](https://composio.dev/toolkits/appcircle/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/appcircle/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/appcircle/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/appcircle/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/appcircle/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get a Appcircle account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Appcircle - Build an agent that connects to Appcircle through MCP - Interact with Appcircle 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 Appcircle MCP server, and what's possible with it? The Appcircle MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Appcircle account. It provides structured and secure access to your mobile CI/CD pipelines, so your agent can perform actions like triggering builds, monitoring workflows, managing artifacts, and automating mobile app deployments on your behalf. - Automated mobile app builds: Let your agent trigger new builds for iOS and Android apps, manage build profiles, and handle build parameters seamlessly. - Workflow monitoring and insights: Enable your agent to fetch real-time statuses, logs, and detailed reports from your Appcircle build and test workflows. - Test execution and results retrieval: Instruct your agent to start automated test runs, collect results, and surface issues or test failures for rapid feedback. - Artifact management and distribution: Have your agent access, download, or distribute app binaries, install links, and build artifacts to your team or testers. - Deployment automation: Direct your agent to publish builds to app stores or internal distribution channels, streamlining release management for your mobile apps. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `APPCIRCLE_BUILD_REPO_WEBHOOK_CALLBACK_STANDARD` | Standard Repo Webhook Callback | Trigger Appcircle builds via Git provider webhook callbacks. This action forwards webhook payloads from GitHub, GitLab, Bitbucket, or Azure DevOps to Appcircle's build webhook endpoint to automatically trigger builds when code is pushed. Use this action when: - Simulating or testing webhook-triggered builds - Programmatically triggering builds using webhook payloads - Integrating custom CI/CD workflows that need to trigger Appcircle builds - Replaying or debugging webhook events Requirements: - The organization must exist and have webhook integration configured in Appcircle - Build profiles must be set up with repository connections - The webhook URL pattern is: https://api.appcircle.io/build/v1/callback/hooks/{provider}/{org_id}/V7 Note: The action returns the raw HTTP response including status code and response body, allowing you to handle success, validation errors, or authentication issues appropriately. | | `APPCIRCLE_BUILD_WEBHOOK_CUSTOM_INTEGRATION` | Custom Integration Webhook Callback | Triggers Appcircle builds via custom integration webhook endpoint by forwarding Git provider webhook payloads. This action is designed to receive and forward webhook payloads from Git providers (GitHub, GitLab, Bitbucket, Azure DevOps) to Appcircle's build system. The webhook URL format and parameters (organization_id, integration_id, version) are provided by Appcircle when you configure custom integrations for repositories connected via SSH or public URL in the build profile settings. Use this action when: - You need to programmatically trigger Appcircle builds from Git provider webhook events - Testing webhook integrations with different payload structures - Implementing custom CI/CD workflows that forward webhook events to Appcircle Note: The organization_id and integration_id values must correspond to actual configurations in Appcircle. Test payloads will typically return 400/404 errors indicating no valid configuration exists for the provided IDs. | | `APPCIRCLE_DISTRIBUTION_LIST_PROFILES` | List Distribution Profiles | List all distribution profiles for the authenticated organization. Distribution profiles are used to manage and distribute app builds to testers. This endpoint supports pagination, sorting, and filtering by profile name. Use this when you need to retrieve available distribution profiles. | | `APPCIRCLE_GET_DISTRIBUTE_SENT_PROFILES` | Get Distribution Sent Profiles | Get distinct profile names for App Sharing Report filter. Returns a list of unique profile names that can be used to filter app sharing reports within the specified date range and organization. Use this to discover available profile names before querying detailed sharing reports. | | `APPCIRCLE_GET_PUBLISH_ACTIVITY_REPORT` | Get Publish Activity Report | Retrieve the publish activity report for your organization. Returns paginated list of publish activities with filtering options by date range, platform, action type, and organization. Use this to monitor and audit publish operations across profiles. | | `APPCIRCLE_LIST_BUILD_PROFILES` | List Build Profiles | List all build profiles for the authenticated organization. Build profiles define the configuration for building mobile applications. Use this to discover available build profiles and their IDs before triggering builds or configuring webhooks. | | `APPCIRCLE_LIST_BUNDLE_IDENTIFIERS` | List Bundle Identifiers | List all bundle identifiers in Appcircle. Returns all bundle identifiers configured in your organization, including their platforms, capabilities, and associated credentials. Use this to discover available bundle identifiers before managing signing identities or app configurations. | | `APPCIRCLE_LIST_ORGANIZATIONS` | List Organizations | List organizations accessible to the authenticated user. Returns a paginated list of organizations with their details including ID, name, logo URL, and SSO status. Supports search filtering and pagination controls. Use this to discover available organizations before performing organization-specific operations like managing builds, distributions, or webhooks. | | `APPCIRCLE_LIST_STORE_PROFILES` | List Store Profiles | List all Enterprise App Store profiles for the authenticated organization. Enterprise App Store profiles are used to distribute apps internally. Use this to discover available store profiles and their IDs before listing app versions or managing store content. | | `APPCIRCLE_RENAME_VARIABLE_GROUP` | Rename Variable Group | Tool to rename an environment group (variable group) in Appcircle. Use when you need to update the name of an existing variable group to better reflect its purpose or environment. | | `APPCIRCLE_STORE_IN_APP_AUTH_TOKEN` | Obtain In-App Update Auth Token | Tool to fetch an access token for Enterprise App Store in-app updates. Use when you have the enterprise store profileId and secret and need to obtain a bearer token for subsequent update requests. | | `APPCIRCLE_STORE_IN_APP_DOWNLOAD_VERSION_WITH_USER` | Download In-App Update Version with User | Tool to download a specific in-app store version and attribute the download to a user for reporting. Use when triggering an in-app update download after obtaining an access token. | | `APPCIRCLE_STORE_INAPP_LIST_APP_VERSIONS` | List Enterprise App Store App Versions | Tool to list available app versions for the Enterprise App Store profile. Use when fetching available in-app update versions. | | `APPCIRCLE_STORE_LIST_PROFILE_APP_VERSIONS_V2` | List Store Profile App Versions V2 | Tool to list app versions under a given store profile. Use when you need to fetch all versions for a specific Enterprise App Store profile after obtaining its ID. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Appcircle MCP server is an implementation of the Model Context Protocol that connects your AI agent to Appcircle. It provides structured and secure access so your agent can perform Appcircle 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 Appcircle 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=["appcircle"], ) 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 Appcircle 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=["appcircle"], ) 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 Appcircle operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Appcircle with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Appcircle using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Appcircle 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 Appcircle MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/appcircle/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/appcircle/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/appcircle/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/appcircle/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/appcircle/framework/codex) - [OpenClaw](https://composio.dev/toolkits/appcircle/framework/openclaw) - [Hermes](https://composio.dev/toolkits/appcircle/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/appcircle/framework/cli) - [LangChain](https://composio.dev/toolkits/appcircle/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/appcircle/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/appcircle/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/appcircle/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/appcircle/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. - [Bolt iot](https://composio.dev/toolkits/bolt_iot) - Bolt IoT is a platform for building and managing IoT projects with cloud-based device control and monitoring. It makes connecting sensors and actuators to the internet seamless for automation and data insights. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Appcircle MCP? With a standalone Appcircle MCP server, the agents and LLMs can only access a fixed set of Appcircle tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Appcircle 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 Appcircle tools. ### Can I manage the permissions and scopes for Appcircle while using Tool Router? Yes, absolutely. You can configure which Appcircle 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 Appcircle data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)