# How to integrate Crowdin MCP with Google ADK

```json
{
  "title": "How to integrate Crowdin MCP with Google ADK",
  "toolkit": "Crowdin",
  "toolkit_slug": "crowdin",
  "framework": "Google ADK",
  "framework_slug": "google-adk",
  "url": "https://composio.dev/toolkits/crowdin/framework/google-adk",
  "markdown_url": "https://composio.dev/toolkits/crowdin/framework/google-adk.md",
  "updated_at": "2026-05-06T08:07:38.198Z"
}
```

## Introduction

This guide walks you through connecting Crowdin to Google ADK using the Composio tool router. By the end, you'll have a working Crowdin agent that can create a new crowdin project for our app, add new source file to the translations project, assign sprint label to specific string ids through natural language commands.
This guide will help you understand how to give your Google ADK agent real control over a Crowdin account through Composio's Crowdin MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Crowdin with

- [OpenAI Agents SDK](https://composio.dev/toolkits/crowdin/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/crowdin/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/crowdin/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/crowdin/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/crowdin/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/crowdin/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/crowdin/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/crowdin/framework/cli)
- [LangChain](https://composio.dev/toolkits/crowdin/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/crowdin/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/crowdin/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/crowdin/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/crowdin/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get a Crowdin account set up and connected to Composio
- Install the Google ADK and Composio packages
- Create a Composio Tool Router session for Crowdin
- Build an agent that connects to Crowdin through MCP
- Interact with Crowdin 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 Crowdin MCP server, and what's possible with it?

The Crowdin MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Crowdin account. It provides structured and secure access to your localization projects, so your agent can manage branches, organize files, label content, automate webhooks, and orchestrate translation workflows on your behalf.
- Branch and project management: Easily have your agent create, delete, or organize Crowdin projects and branches to streamline new releases or features.
- Dynamic file handling: Let your agent add new files to projects, ensuring your translation assets are always up to date and properly organized by branch or directory.
- Labeling and content categorization: Direct your agent to create, assign, or remove labels on resources and strings, helping you segment and track translation tasks with precision.
- Workflow automation with webhooks: Automate your translation process by having the agent set up or remove webhooks for real-time notifications and integrations.
- Resource cleanup and maintenance: Empower your agent to delete obsolete branches, labels, webhooks, or entire projects, keeping your Crowdin workspace clean and focused.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `CROWDIN_ADD_BRANCH` | Add Branch | Tool to create a new branch in a crowdin project. use when you need to isolate translations for a new feature or release. |
| `CROWDIN_ADD_FILE` | Add File | Tool to add a new file to a crowdin project. use after uploading the file to storage to place it under the specified project, branch, or directory. |
| `CROWDIN_ADD_LABEL` | Add Label | Tool to create a new label in a crowdin project. use when you need to tag resources with a custom identifier, such as 'sprint-5'. |
| `CROWDIN_ADD_PROJECT` | Create Crowdin Project | Tool to create a new project in crowdin. use before uploading source files to initialize translation workflows. |
| `CROWDIN_ADD_WEBHOOK` | Add Webhook | Tool to create a new webhook in a crowdin project. use after confirming the project id and desired event triggers. |
| `CROWDIN_ASSIGN_LABEL_TO_STRINGS` | Assign Label to Strings | Tool to assign the specified label to provided string ids in a project. use after creating the label or verifying string ids to categorize content. |
| `CROWDIN_DELETE_BRANCH` | Delete Branch | Tool to delete a specific branch from a crowdin project. use when you need to remove an obsolete branch after it's fully merged. |
| `CROWDIN_DELETE_LABEL` | Delete Label | Tool to delete the label identified by the specified label id in a project. use when you need to remove outdated or incorrect labels. ensure no resources reference the label before deletion. |
| `CROWDIN_DELETE_PROJECT` | Delete Project | Tool to delete a crowdin project by its id. use when you need to permanently remove a project after confirming no further usage. ensure all resources are no longer needed before deletion. |
| `CROWDIN_DELETE_WEBHOOK` | Delete Webhook | Tool to delete the webhook identified by the specified webhook id in a crowdin project. use when you need to remove obsolete or incorrect webhooks after confirming project and webhook ids. |
| `CROWDIN_EDIT_FILE` | Edit File | Tool to update file details in a project. use after confirming valid project and file ids. |
| `CROWDIN_EDIT_LABEL` | Edit Label | Tool to edit a label in a crowdin project. use when you need to update the name or description of an existing label. ensure the label exists before using. example: edit label 42 to 'release-1.1'. |
| `CROWDIN_EDIT_PROJECT` | Edit Project | Tool to update project details using json-patch. use after confirming project settings to modify metadata like name, description, visibility, or languages. |
| `CROWDIN_EDIT_STRING` | Edit String | Tool to update string details in a crowdin project. use when you need to modify a string's text or metadata after creation. |
| `CROWDIN_GET_LABEL` | Get Label | Tool to retrieve information about the label identified by the specified label id in a project. use after confirming the project context to fetch label details. |
| `CROWDIN_GET_LANGUAGE` | Get Language | Tool to retrieve details of a specific language. use when you have a language identifier and need locale codes and plural rules before configuring translations. |
| `CROWDIN_GET_MEMBER_INFO` | Get Member Info | Tool to retrieve information about a project member. use when you need to inspect details for a specific user within a project after obtaining their member id. |
| `CROWDIN_GET_PROJECT` | Get Project | Tool to retrieve details of a specific crowdin project. use when you need to inspect project settings before making updates. |
| `CROWDIN_GET_STRING` | Get String | Tool to retrieve details of a specific string in a crowdin project. use after confirming the project and string ids to fetch its metadata. |
| `CROWDIN_GET_WEBHOOK` | Get Webhook | Tool to retrieve information about the webhook identified by the specified webhook id in a project. use after confirming the project context to fetch webhook details. |
| `CROWDIN_LIST_BRANCHES` | List Branches | Tool to list all branches in a crowdin project. use after selecting a project to view its branch structure. supports pagination and optional filtering by branch id. |
| `CROWDIN_LIST_FILES` | List Files | Tool to list files in a crowdin project. use when you need to retrieve a list of project files with optional filters by directory, group, or branch before processing. |
| `CROWDIN_LIST_LABELS` | List Labels | Tool to list labels in a crowdin project. use when you need to retrieve all labels for a specific project with optional pagination. |
| `CROWDIN_LIST_LANGUAGES` | List Languages | Tool to retrieve a list of supported languages. use when you need to fetch all languages crowdin supports before starting localization. |
| `CROWDIN_LIST_PROJECT_MEMBERS` | List Project Members | Tool to list members in a crowdin project. use when you need to retrieve project member list for management tasks after confirming the project id. |
| `CROWDIN_LIST_PROJECTS` | List Projects | Tool to retrieve a list of all crowdin projects with optional filters. use when you need to paginate through or filter projects by owner, group, language inclusion, or archive status. |
| `CROWDIN_LIST_REPORTS` | List Reports | Tool to list reports for a given crowdin project. use after confirming project id to retrieve available reports. supports pagination via limit and offset. |
| `CROWDIN_UPLOAD_STORAGE` | Upload Storage | Tool to upload a file to crowdin storage. use when you need to obtain a storageid for further operations like adding files to a project. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Crowdin MCP server is an implementation of the Model Context Protocol that connects your AI agent to Crowdin. It provides structured and secure access so your agent can perform Crowdin 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 Crowdin 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=["crowdin"],
)

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 Crowdin 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=["crowdin"],
)

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 Crowdin operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
```

## Conclusion

You've successfully integrated Crowdin with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Crowdin using natural language commands.
Key takeaways:
- The Tool Router approach dynamically routes requests to the appropriate Crowdin 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 Crowdin MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/crowdin/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/crowdin/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/crowdin/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/crowdin/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/crowdin/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/crowdin/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/crowdin/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/crowdin/framework/cli)
- [LangChain](https://composio.dev/toolkits/crowdin/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/crowdin/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/crowdin/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/crowdin/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/crowdin/framework/crew-ai)

## Related Toolkits

- [Apilio](https://composio.dev/toolkits/apilio) - Apilio is a home automation platform that lets you connect and control smart devices from different brands. It helps you build flexible automations with complex conditions, schedules, and integrations.
- [Basin](https://composio.dev/toolkits/basin) - Basin is a no-code form backend for quickly setting up reliable contact forms. It lets you collect and manage form submissions without writing any server-side code.
- [Bouncer](https://composio.dev/toolkits/bouncer) - Bouncer is an email validation platform that verifies the authenticity of email addresses in real-time and batch. It helps boost deliverability and reduce bounce rates for your communications.
- [Conveyor](https://composio.dev/toolkits/conveyor) - Conveyor is a platform that automates security reviews with a Trust Center and AI-driven questionnaire automation. It streamlines compliance and vendor security processes for faster, hassle-free reviews.
- [Databox](https://composio.dev/toolkits/databox) - Databox is a business analytics platform that connects your data from any tool and device. It helps you track KPIs, build dashboards, and discover actionable insights.
- [Detrack](https://composio.dev/toolkits/detrack) - Detrack is a delivery management platform for real-time tracking and proof of delivery. It helps businesses automate notifications and keep customers updated every step of the way.
- [Dnsfilter](https://composio.dev/toolkits/dnsfilter) - Dnsfilter is a cloud-based DNS security and content filtering solution. It helps organizations block online threats and manage safe internet access with ease.
- [Faraday](https://composio.dev/toolkits/faraday) - Faraday lets you embed AI in workflows across your stack for smarter automation. It boosts your favorite tools with actionable intelligence and seamless integration.
- [Feathery](https://composio.dev/toolkits/feathery) - Feathery is an AI-powered platform for building dynamic data intake forms with advanced logic. It helps teams automate complex workflows and collect structured data with ease.
- [Fillout forms](https://composio.dev/toolkits/fillout_forms) - Fillout forms is an online platform for building and managing forms with a flexible API. It lets you create, distribute, and collect responses from forms with ease.
- [Formdesk](https://composio.dev/toolkits/formdesk) - Formdesk is an online form builder for creating and managing professional forms. It's perfect for collecting data, automating workflows, and integrating form submissions with your favorite services.
- [Formsite](https://composio.dev/toolkits/formsite) - Formsite lets you build online forms and surveys with drag-and-drop simplicity. Capture, manage, and integrate form responses securely for streamlined workflows.
- [Graphhopper](https://composio.dev/toolkits/graphhopper) - GraphHopper is an enterprise-grade Directions API for routing, optimization, and geocoding across multiple vehicle types. It enables fast, reliable route planning and logistics automation for businesses.
- [Hyperbrowser](https://composio.dev/toolkits/hyperbrowser) - Hyperbrowser is a next-generation platform for scalable browser automation. It empowers AI agents to interact with web apps, automate workflows, and handle browser sessions at scale.
- [La Growth Machine](https://composio.dev/toolkits/lagrowthmachine) - La Growth Machine automates multi-channel sales outreach and routine tasks for sales teams. Streamline your workflow and focus on closing more deals.
- [Leverly](https://composio.dev/toolkits/leverly) - Leverly is a workflow automation platform that connects and coordinates actions across your apps. It streamlines repetitive processes so your business runs smoother, faster, and with fewer manual steps.
- [Maintainx](https://composio.dev/toolkits/maintainx) - Maintainx is a cloud-based CMMS for centralizing maintenance data, communication, and workflows. It helps organizations streamline maintenance operations and improve team coordination.
- [Make](https://composio.dev/toolkits/make) - Make is an automation platform that connects your favorite apps and services. Build powerful, custom workflows without writing code.
- [Ntfy](https://composio.dev/toolkits/ntfy) - Ntfy is a notification service to send push messages to phones or desktops. Instantly deliver alerts and updates to users, devices, or teams.
- [Persona](https://composio.dev/toolkits/persona) - Persona offers identity infrastructure to automate user verification and compliance. It helps organizations securely verify users and reduce fraud risk.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Crowdin MCP?

With a standalone Crowdin MCP server, the agents and LLMs can only access a fixed set of Crowdin tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Crowdin 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 Crowdin tools.

### Can I manage the permissions and scopes for Crowdin while using Tool Router?

Yes, absolutely. You can configure which Crowdin 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 Crowdin data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)