localingos
AI-powered app translation for developers.
What it can do
- Localingos Sync: Push source strings to Localingos and pull back translations.
- Localingos Get Translations: Get all translations for a project.
- Localingos Get Translatables: Get all source strings for a project.
What data it sees
Do you need an account
An API key from the service settings is required
AI-powered app translation for developers. Push your source strings, get translations back in 50+ languages automatically.
What it does
Localingos translates your application strings using AI (Amazon Bedrock Claude). Connect your AI assistant to Localingos and manage your entire i18n workflow without leaving your editor.
Tools
- localingos_sync — Push source strings and pull translations in one step
- localingos_push — Push source strings to Localingos
- localingos_get_translations — Retrieve translations for your project
- localingos_get_translatables — List all source strings
- localingos_family_members — List project members
- localingos_add_member / localingos_remove_member — Manage project access
- localingos_billing_status — Check subscription and usage
- localingos_attach_billing / localingos_detach_billing — Manage billing for projects
Getting started
- Sign up at https://localingos.com (free — 5,000 words, no credit card)
- Create a project and an API key
- Add the server config to your AI assistant
- Start translating with natural language commands
Supports 50+ languages, JSON formats, and works with Claude Desktop, Cursor, Kiro, and any MCP-compatible client.
How to connect
How to connect localingos to Claude
The server address to paste into Claude settings:
https://localingos--juhsis.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect localingos to ChatGPT
The server address to paste into ChatGPT settings:
https://localingos--juhsis.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect localingos to Cursor
The server address to paste into Cursor settings:
https://localingos--juhsis.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (18)
Raw names from tools/list. Only developers need these.
| localingos_sync | Push source strings to Localingos and pull back translations. |
| localingos_get_translations | Get all translations for a project. |
| localingos_get_translatables | Get all source strings for a project. |
| localingos_push | Push source strings without pulling translations. |
| localingos_project_members | List members of a project. |
| localingos_add_member | Add a member to a project (admin only). |
| localingos_remove_member | Remove a member from a project (admin only). |
| localingos_billing_status | Show billing status for a project — plan, usage, owner. |
| localingos_attach_billing | Attach your billing account to a project. |
| localingos_detach_billing | Detach billing from a project. Project becomes read-only. |
| localingos_list_projects | List all projects the authenticated user has access to. |
| localingos_delete_translatables | Delete source strings from a project by their foreign IDs. Used for pruning stale keys. |
| localingos_get_translation | Get all translations for a single source string (by foreign ID / key name). |
| localingos_get_translations_batch | Get translations for multiple source strings at once. |
| localingos_update_translations | Create or update translations manually. Useful for correcting AI translations or adding human translations. |
| localingos_translation_jobs | List translation jobs for a project. Optionally filter by state (QUEUED, IN_PROGRESS, DONE, FAILED, BLOCKED). |
| localingos_retry_job | Retry a single failed translation job. |
| localingos_retry_all_jobs | Retry all failed and blocked translation jobs in a project. |