kilo-dev

The kilo-dev MCP server exposes a set of i18n tools that help manage translation data stored in JSON locale files used by the Kilo Code extension. It runs via MCP over stdio and provides four main tools: translate_i18n_key to translate a given key across locales, move_i18n_key to relocate a key from one file to another across all locales, list_locales to enumerate available locales, and remove_i18n_keys to delete specified keys from all locale files. To use these tools, configure the server in your global MCP setup (as shown in the example) so your AI assistant can call the appropriate tool based on natural language prompts. When you prompt the AI, it will select the correct tool and execute translations or file operations accordingly. For translating keys, the AI will target the core translation set unless directed otherwise; for listing locales, it will show all locales supported by the webview UI; moving keys will propagate the change across all locale files; removing keys will prune obsolete entries from all locales.

Prerequisites:

• Node.js and npm installed on your machine
• Access to the project repository containing the kilo-dev MCP server
• An OpenRouter API key if using translation features

1. Clone the repo or navigate to your working directory:

git clone https://github.com/your-org/kilo-org-kilo-dev-mcp-server.git
cd kilo-org-kilo-dev-mcp-server

2. Install dependencies:

npm install

3. Prepare configuration:

• Ensure you have an OpenRouter API key and set it in your environment or a local .env file.
• If needed, adjust the path in the MCP setup to point to your local kilo-dev-mcp-server directory.

4. Run the i18n MCP server toolset:

npm run mcp:i18n

5. Integrate with your global MCP config (example shown in the README) to enable stdio-based communication with your AI assistant.

Notes and tips:

• The i18n tools operate on JSON locale files used by the Kilo Code extension; ensure your locale files are in the expected structure.
• The OPENROUTER_API_KEY is required for translation functionality; keep it secure and do not hard-code it in the repository.
• If you encounter timeouts, adjust the timeout value in your MCP configuration or increase the runtime resources.
• The alwaysAllow list controls which tools are exposed through the MCP; add or remove tools as needed for your deployment.
• When moving or removing keys, ensure there are no references in code or UI dependencies that rely on those keys to avoid runtime errors.