MCP Localization Manager Guide

MCP Integration for AI Translation Workflows

Use this page when you want to connect Goman Live through MCP clients and operate localizations from IDE chat with context-aware AI workflows.

🔗

Native MCP Integration

Create and manage localization keys from IDE chat (Cursor / VS Code) and refine results in the web app.

🤖

AI-Powered Translations

AI translations with context awareness that reuse existing terminology for more consistent output.

🌐

URL-Accessible Translations

Fetch translations via URL for easy integration and live previews.

⚙️

Prompt & Context Management

Centralize prompts and context so translation tone stays stable across releases.

Who is it for?

Product teams and developers who want IDE-native translation operations through MCP with centralized control over context and prompts.

Get started

Start by configuring your MCP client, then trigger language and localization operations from chat and refine output in Goman Live.

MCP Setup and Usage Examples

Below is a short guide for configuring MCP in supported clients and using chat prompts to create and manage localizations.

1
MCP Client Setup

Client:

.vscode/mcp.json

{
  "servers": {
    "goman-mcp": {
      "type": "streamable-http",
      "url": "https://mcp.goman.live/mcp",
      "headers": {
        "apiKey": "<YOUR_API_KEY>",
        "applicationid": "<YOUR_APPLICATION_ID>"
      }
    }
  }
}

2
What the Goman MCP server can do

Typical actions you can trigger directly from IDE chat:

List active localization languages for your application

Find an existing translation by key and check whether it exists

Create or update a localization across multiple languages

Delete an obsolete localization key

Sample natural-language prompts:

- Show active languages for goman-mcp
- Find localization by key "app.header.title"
- Create/update key "translations.edit.settings.use_rag":
  be="Выкарыстоўваць RAG", en="Use RAG", ru="Использовать RAG"
- Delete the key "obsolete.key" across all languages

3
Recommendations

Use namespaces in keys (e.g., app.header.title).

Keep API keys and applicationId in environment variables, not in public code.

Add a fallback: if a translation is missing, show the key.

Ensure the correct MCP server goman-mcp is selected in IDE chat.

4
Troubleshooting

401/403: check apiKey and permissions. Don't commit keys, use IDE/CI secrets.

404/422: verify applicationid and localization key format (whitespace, proper namespace).

Browser CORS: call from server (Server Components / API routes) or configure a proxy.

For more details and examples, ask in your IDE chat and trigger actions through the goman-mcp server.