Crowdin MCP integration for AI agents.
Connect AI agents to Crowdin through 7 structured actions, including list branches, create branch, and create directory. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- OAuth 2.0 + API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Crowdin integration exposes
The Crowdin Agent App exposes 7 provider-backed actions for productivity and communication work. Its current contract lets an authorized agent list crowdin project branches, create a crowdin project branch, and create a crowdin directory. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Crowdin account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Crowdin capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_branchesREADList Crowdin project branches.
INPUTS: projectId / limit / offset / name
create_branchWRITECreate a Crowdin project branch.
INPUTS: projectId / name / title / exportPattern / priority
create_directoryWRITECreate a Crowdin directory.
INPUTS: projectId / name / branchId / directoryId / title
list_directoriesREADList Crowdin directories.
INPUTS: projectId / branchId / directoryId / filter / recursion
list_filesREADList Crowdin source files.
INPUTS: projectId / branchId / directoryId / filter / recursion
list_projectsREADList Crowdin projects.
INPUTS: limit / offset
upload_fileWRITEUpload a source file to Crowdin.
INPUTS: projectId / name / contentBase64 / contentType / branchId
INPUT CONTRACTS
Know what the action needs before it runs.
list_branches
projectIdREQUIRED- The project ID to list branches for.
limitOPTIONAL- The maximum number of items to return.
offsetOPTIONAL- The offset for paginating through results.
nameOPTIONAL- The branch name to filter by.
create_branch
projectIdREQUIRED- The project ID to create the branch in.
nameREQUIRED- The name of the new branch.
titleOPTIONAL- The title of the new branch.
exportPatternOPTIONAL- The export pattern for the branch.
priorityOPTIONAL- The priority of the branch.
create_directory
projectIdREQUIRED- The project ID to create the directory in.
nameREQUIRED- The name of the new directory.
branchIdOPTIONAL- The branch ID to filter or create within.
directoryIdOPTIONAL- The directory ID to filter or create within.
titleOPTIONAL- The title of the new directory.
list_directories
projectIdREQUIRED- The project ID to list directories for.
branchIdOPTIONAL- The branch ID to filter or create within.
directoryIdOPTIONAL- The directory ID to filter or create within.
filterOPTIONAL- The filter string to match directory names.
recursionOPTIONAL- Whether to list directories recursively.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Branches
List Crowdin project branches. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_branchesControl Create Branch
Create a Crowdin project branch. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_branchVerify with List Directories
List Crowdin directories. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_directoriesSAFETY BOUNDARY
Operate Crowdin with explicit limits
- Authorize Crowdin with OAuth 2.0 and API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- The sampled contract declares provider scopes including `crowdin.source.write`, `crowdin.source.read`, and `crowdin.projects.read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Crowdin task completed successfully.
CONNECTION MODEL
OAuth 2.0 + API key
Crowdin personal access token used with the Authorization Bearer header. Create or manage it at https://crowdin.com/settings#api-key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Crowdin.