Integration

Crowdin integration

Localization and translation management platform API. Manage translation projects, upload source files, download translations, and collaborate with translators. Features include translation memory, machine translation, in-context editing, and integrations. Used by Microsoft, Uber, and Mozilla for software localization at scale.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Crowdin.Built from the 32 Crowdin tools below, on the connection you add once.

Common Crowdin use cases

  • version control
  • CI/CD integration
  • deployment
  • project setup
  • CI/CD pipeline
  • content removal
  • file organization
  • progress tracking
  • file sync
  • CI/CD sync

What you can do with Crowdin

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

File, 6 operations

  • add_fileAdd filePOSTAdds a source file to a project for translation. Specify storage ID from upload and file options. Crowdin parses content into translatable strings.
  • delete_fileDelete fileDELETEDeletes a source file from the project. Removes the file and all associated strings and translations.
  • download_fileDownload fileGETDownloads a source file. Returns a temporary URL to download the file content.
  • get_fileGet fileGETGets details for a specific source file. Returns file name, path, type, word count, and revision number.
  • list_filesList filesGETLists source files in a translation project. Returns file IDs, names, paths, and word counts. Filter by directory or branch for nested structures.
  • update_fileUpdate filePUTUpdates source file content. Crowdin intelligently handles string changes - keeps translations for unchanged strings. Options control behavior for modified strings.

Translation, 6 operations

  • build_project_translationBuild project translationPOSTBuilds translated files for download. Generates translation outputs for specified languages. Returns build ID for status tracking and download.
  • check_build_statusCheck build statusGETChecks the status of a translation build. Returns progress percentage and status (inProgress, finished, failed).
  • download_translationsDownload translationsGETDownloads completed translation build. Returns URL to ZIP file containing all translated files. Files organized by language.
  • export_project_translationExport project translationPOSTExports translations for a specific language. Returns a download link without creating a full project build.
  • list_buildsList buildsGETLists translation builds for a project. Returns build history with status and progress.
  • upload_translationUpload translationPOSTUploads existing translations for a language. Imports translation files to match source strings.

Progress, 5 operations

  • get_branch_progressGet branch progressGETGets translation progress per language for a specific branch.
  • get_directory_progressGet directory progressGETGets translation progress per language for a specific directory.
  • get_file_progressGet file progressGETGets translation progress per language for a specific file. Returns completion percentages and word/phrase counts per language.
  • get_language_progressGet language progressGETGets translation progress per file for a specific language. Returns completion details per file.
  • get_translation_progressGet translation progressGETGets translation progress per target language. Returns translation percentage, approval percentage, and word counts for tracking localization status.

Storage, 4 operations

  • delete_storageDelete storageDELETEDeletes a file from temporary storage. Frees storage space for files no longer needed.
  • get_storageGet storageGETGets details of a specific storage file. Returns storage ID and file name.
  • list_storagesList storagesGETLists files in temporary storage. Returns storage IDs and file names. Storage files persist for 24 hours.
  • upload_storageUpload storagePOSTUploads a file to Crowdin storage. Returns storage ID for use in add/update file operations. First step in file upload workflow.

Project, 3 operations

  • delete_projectDelete projectDELETEDeletes a translation project. This permanently removes the project and all associated data.
  • get_projectGet projectGETGets detailed project information. Returns source language, target languages, translation progress, QA settings, and project configuration.
  • list_projectsList projectsGETLists all translation projects in your Crowdin account. Returns project details including languages, status, and translation progress.

String, 3 operations

  • add_stringAdd stringPOSTAdds a new source string to a project. Creates a translatable string with text, identifier, and context.
  • delete_stringDelete stringDELETEDeletes a source string and all its translations from the project.
  • list_source_stringsList source stringsGETLists source strings for translation. Returns string ID, text, context, and identifier. Filter by file, branch, directory, labels, or search text.

Branch, 2 operations

  • create_branchCreate branchPOSTCreates a branch in the project. Maps to version control branches for parallel translation workflows.
  • list_branchesList branchesGETLists branches in a project. Returns branch IDs and names for version-controlled translation content.

Directory, 2 operations

  • create_directoryCreate directoryPOSTCreates a directory in the project. Organizes source files into a folder structure.
  • list_directoriesList directoriesGETLists directories in a project. Returns directory IDs, names, and paths for organizing source files.

Language, 1 operation

  • list_languagesList languagesGETLists all supported languages in Crowdin. Returns language IDs, names, and locale information.

Use Crowdin from Claude Code, Cursor or Codex

Connect Crowdin in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Crowdin operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Crowdin

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Crowdin once

    Add your Crowdin connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Crowdin integration FAQ

What can you do with the Crowdin integration?

LiveContext exposes 32 operations on Crowdin, covering file, translation, progress and storage. Common uses include version control, CI/CD integration and deployment.

Popular integrations

Browse the whole catalog