MCP Localization Manager

AI Translations with Context & Prompt Control

Goman Live is a localization manager built for developers and content teams. We translate with AI, support the Model Context Protocol (MCP), provide URL-based access to translations, and include built-in context and prompt management for quality and consistency.

🔗

Native MCP Integration

Create and manage localization keys from your IDE chat (Cursor / VS Code) and use the web app for full AI translation management.

🤖

AI-Powered Translations

AI translations with context awareness — reuse existing translations and terminology for better results.

🌐

URL-Accessible Translations

Fetch translations via URL for easy integration and previews.

⚙️

Prompt & Context Management

Centralize and version prompts to guide translation style and tone.

Who is it for?

Product teams, developers, and localization managers who need reliable, automated translations with full control over prompts, context, and developer workflows.

Get started

Try the MCP flow in your IDE, then refine translations in the Goman web platform. You can also access translations via URL and export production-ready files.

MCP Setup & Usage Examples

Below is a short guide for configuring MCP in VS Code / Cursor and examples of how to use it to create and manage localizations. Do not store secrets in source code—use environment variables or editor secrets.

1IDE setup (VS Code / Cursor)

Editor:

.vscode/mcp.json

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

2What 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 if 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

3Recommendations

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.

4Troubleshooting

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 select an MCP action. For ready-made import/export workflows, use the Goman web platform.