loco

This MCP server provides translation management tools powered by the Loco API. It exposes capabilities to list, create, update, and delete translation assets, fetch and update translations across locales, and manage tags on assets. To use these tools, you’ll configure the loco MCP server in your MCP setup, then invoke commands such as list_assets, create_asset, update_asset, delete_asset, get_translation, update_translation, and tag_asset. Each tool requires a valid Loco API key as a parameter, which authorizes access to your Loco project data. When configuring tools, supply the API key in the command parameters as shown in typical tool invocations. You can find your API key in your Loco project under Developer Tools → API Keys (Full Access Key).

Prerequisites:

• Node.js (with npm or pnpm)
• Access to the internet to install npm packages

Installation steps:

1. Install Node.js if you haven’t already. You can download it from https://nodejs.org/
2. Install the loco-mcp package using npx (as shown in the usage example) or install globally if you prefer:
   • Using npx for one-off runs: npx -y loco-mcp
   • Or installing locally in a project: npm install loco-mcp
3. Ensure your environment can access the Loco API by having a valid API key ready (see the developer docs in Loco for generating keys).
4. Configure your MCP to reference the loco MCP server using the provided mcp_config example in your environment or orchestrator configuration.

Notes and tips:

• Each tool requires a Loco API key as a parameter. Do not forget to pass the API key when calling tools like list_assets, create_asset, get_translation, update_translation, etc.
• If you’re using npx to run loco-mcp, ensure your environment can fetch and execute the package from the npm registry.
• Handle API rate limits by implementing retries with backoff in your integration if you plan to automate translations at scale.
• You can manage assets and translations across multiple locales by using the corresponding tools in sequence (e.g., create_asset, then update_translation for different locales).
• For asset tagging, use the tag_asset or corresponding tag management tools exposed by the MCP server.
• If you encounter issues, verify that the API key has the necessary permissions in Loco (Full Access Key) and that your network can reach Loco’s API endpoints.