Crowdin
Crowdin is a localization management platform that streamlines the translation process, offering tools for collaboration, content centralization, and workflow automation.
Verdict
Common use cases
- Create release branches for each sprint
- Upload new UI strings before dev handoff
- Tag strings by feature for translator context
- Check translation progress during standups
- Set up webhooks to alert on completion
Integration
- Vendor
- Crowdin
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 28
- Composio slug
crowdin
Tools
- 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.
- 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.
- 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'.
- Add Webhook
Tool to create a new webhook in a crowdin project. use after confirming the project id and desired event triggers.
- 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.
- Create Crowdin Project
Tool to create a new project in crowdin. use before uploading source files to initialize translation workflows.
- Delete Branchdestructive
Tool to delete a specific branch from a crowdin project. use when you need to remove an obsolete branch after it's fully merged.
- Delete Labeldestructive
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.
- Delete Projectdestructive
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.
- Delete Webhookdestructive
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.
- Edit File
Tool to update file details in a project. use after confirming valid project and file ids.
- 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'.
- Edit Project
Tool to update project details using json-patch. use after confirming project settings to modify metadata like name, description, visibility, or languages.
- 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.
- 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.
- 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.
- 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.
- Get Project
Tool to retrieve details of a specific crowdin project. use when you need to inspect project settings before making updates.
- 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.
- 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.
- 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.
- 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.
- 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.
- List Languages
Tool to retrieve a list of supported languages. use when you need to fetch all languages crowdin supports before starting localization.
- 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.
- 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.
- 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.
- 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.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select Crowdin from the list. 3. Go to your Crowdin account settings, generate a Personal Access Token with 'Project' scope (read and write), and copy it. 4. Paste the token into Switchy's API Key field and click 'Connect'. 5. Switchy will verify the token and list your accessible projects. 6. Open any Space, type '@Crowdin list my projects' and send — if you see project names in the reply, the connection works. 7. To invoke a tool, @mention Crowdin with a task like '@Crowdin create a branch called feature-checkout in project 12345' and the MCP will execute it immediately.
What teammates see: by default, memories from Crowdin are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Feature Branch
@Crowdin create a branch named 'v2-onboarding' in project 98765. Use this branch to track all strings for the new user onboarding flow.Open in a Space →
Upload Source File
@Crowdin upload the file 'en-US.json' to project 98765 under the 'mobile-app' directory. The file is already in storage and ready to import.Open in a Space →
Label Strings by Sprint
@Crowdin create a label called 'sprint-12' in project 98765, then assign it to string IDs 4401, 4402, and 4403. This groups all checkout flow strings for the current sprint.Open in a Space →
Check Translation Status
@Crowdin show me the translation progress for the 'v2-onboarding' branch in project 98765. I need to know if we're ready to ship French and German.Open in a Space →
Set Up Completion Webhook
@Crowdin add a webhook to project 98765 that fires on 'translation.completed' events. Send the payload to https://hooks.example.com/crowdin so we get notified in Slack.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Crowdin list all translation strings tagged with 'sprint-5' and show their current completion status across French and German
Found 47 strings tagged 'sprint-5' in your project. French translation is 89% complete (42/47 strings approved), with 3 strings in review and 2 untranslated. German is at 72% (34/47 approved), with 8 strings awaiting review and 5 untranslated. The highest-priority untranslated strings are in the onboarding flow ('welcome_title', 'setup_instructions'). All strings were added to the project within the last 14 days.
This example shows Crowdin's read capabilities for tracking localization progress by label. Requires a valid API key with project-read scope. The MCP returns current state at query time — completion percentages will shift as translators work. Label-based filtering only works if you've previously used the 'Add Label' and 'Assign Label to Strings' tools.
@Crowdin create a new branch called 'feature-checkout-v2', then upload the file 'checkout-strings.json' from our repo to that branch
Branch 'feature-checkout-v2' created successfully in project ID 482301. Uploaded 'checkout-strings.json' (34 source strings detected) to the new branch. Crowdin parsed 34 translatable keys including payment flow labels and error messages. The file is now visible to your translation team under the feature branch, isolated from the main branch until you're ready to merge. No translations have started yet — strings are queued for the 6 target languages configured in your project.
This example demonstrates Crowdin's write workflow for feature-branch translation isolation. The 'Add Branch' and 'Add File' tools execute sequentially — the file upload requires the branch to exist first. You'll need write permissions on the project. Be aware that creating branches and uploading files are quota-limited actions on some Crowdin plans; check your account limits before automating bulk uploads.
@Crowdin pull the last 20 approved translations for Spanish, then draft a changelog entry summarizing what UI text changed this week
Retrieved 20 recently approved Spanish translations (approved between Jan 6–12). Changes span three areas: (1) Dashboard navigation — 'Configuración' replaced 'Ajustes' for consistency, 'Informes' updated to 'Reportes' per regional preference. (2) Error messages — 5 strings reworded for clarity, notably 'No se pudo cargar' now 'Error al cargar datos'. (3) Onboarding flow — 'Comenzar' changed to 'Empezar ahora' to match A/B test winner. Changelog draft: 'Spanish localization updates include standardized navigation terms, clearer error messaging, and onboarding CTA refinement based on user testing.' All changes maintain tone and comply with your style guide.
This synthesis example pairs Crowdin's translation history with the AI's summarization. The MCP fetches approved translation records; the AI interprets patterns and drafts human-readable release notes. Useful for keeping non-technical stakeholders informed about localization work. Note that 'approved' status depends on your project's workflow settings — if you don't require approval steps, you may need to query by date range instead.
Use-case deep-dives
When Crowdin MCP fits fast-moving product teams
A 6-person product team ships features every two weeks and needs translations ready before each release. The Crowdin MCP lets your AI create a branch per feature, upload strings, assign sprint labels, and delete the branch after merge—all without leaving your chat. This works when your translation volume is predictable (under 500 strings per sprint) and your translators use Crowdin's web UI for the actual work. If you're shipping daily or managing 10+ languages with complex review workflows, the 28-tool surface gets noisy; you'll spend more time explaining context to the AI than clicking buttons yourself. For teams running two-week sprints with 3-5 languages, this MCP turns localization setup into a five-minute standup task instead of a half-hour context switch.
Why Crowdin MCP works for help-center ops
A 3-person support team maintains a 200-article help center in four languages and adds 8-12 articles per month. The Crowdin MCP handles the upload-label-webhook loop: your AI uploads new markdown files, tags them with the current quarter label, and sets a webhook to ping Slack when translations land. This keeps the team in their existing tools (Notion for drafts, Slack for alerts) instead of logging into Crowdin daily. The boundary: if your articles reference each other heavily or need version control beyond branches, the MCP's file-add tool won't capture dependencies—you'll need Crowdin's CLI or API for batch imports with metadata. For straightforward monthly publishing with simple tagging, this MCP cuts the coordination overhead from 90 minutes a month to 10.
When Crowdin MCP speeds up agency onboarding
A localization agency onboards 4-6 new clients per quarter, each needing a fresh Crowdin project with standard labels, webhooks, and branch structure. The Crowdin MCP lets account managers scaffold a project in chat: create project, add three branches (dev, staging, prod), apply client-specific labels, configure delivery webhooks—done in one conversation instead of six browser tabs. This wins when your project templates are consistent and you're not customizing workflows per client. If every client needs unique TM rules, custom file parsers, or integration with their CMS, the MCP's 28 tools won't cover the edge cases and you're back in the Crowdin dashboard anyway. For agencies running repeatable onboarding with 80% template overlap, this MCP turns a 45-minute setup checklist into a three-minute AI handoff.
Frequently asked
What does the Crowdin MCP do in Switchy?
The Crowdin MCP lets your team manage translation projects directly from Switchy — create projects, add source files, organize content with branches and labels, and set up webhooks for event-driven workflows. You can automate repetitive localization tasks without switching to the Crowdin dashboard. It's built for teams running continuous localization alongside their development cycle.
Do I need admin access to connect Crowdin?
You need a Crowdin API key with project-level permissions. Typically this means you're a project manager or owner in Crowdin, not just a translator. The key must allow creating projects, uploading files, and managing webhooks if you want the full 28 tools. Check your Crowdin account settings under API to generate a key with the right scopes.
Can the Crowdin MCP translate files automatically?
No. This MCP manages the structure and workflow — branches, files, labels, webhooks — but doesn't trigger machine translation or assign human translators. You still configure translation engines and workflows inside Crowdin itself. Think of it as the scaffolding tool: it sets up projects and organizes content so your translation process can run smoothly.
Why use this instead of the Crowdin web UI?
Use the MCP when you want to script or automate localization steps alongside other work in Switchy. For example, create a branch and upload files in one prompt after a feature ships, or assign labels to strings as part of a sprint workflow. The web UI is fine for one-off tasks; the MCP shines when localization is part of a repeatable process.
Who on the team should connect this integration?
Whoever owns your localization pipeline — usually a product manager, release engineer, or developer who coordinates translations. They'll need access to your Crowdin account and the authority to create API keys. Once connected, anyone in your Switchy workspace can invoke the tools, but only the connector's API key is used for authentication.