Locize
About
Locize TMS: 26 tools for translations, TM/glossary/styleguide/screenshot context, versions. OAuth.
Details
- Author
- Unknown
- Categories
- Developer Tools, Other, Automation, API
Jump to
The Locize MCP (Model Context Protocol) server lets AI assistants (Claude, Cursor, GitHub Copilot, and others) interact directly with your translation projects.
claude mcp add --transport http locize https://mcp.locize.app
Then run/mcpin a Claude Code session and complete the OAuth flow.
Note:After first-time OAuth, Claude Code may show"Authentication successful, but server reconnection failed."This is aknown Claude Code issue; simply restart Claude Code and the server will connect automatically using the stored token.
Other HTTP-native clients (Cursor, VS Code, etc.)
Add the server URLhttps://mcp.locize.appin your client's MCP settings and complete the OAuth flow. The exact steps vary by client; consult your client's MCP documentation.
For clients that support stdio but not HTTP, usemcp-remoteas a bridge:
{ "mcpServers": { "locize": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.locize.app"] } } }
The MCP server supports two authentication methods:
OAuth 2.0 (recommended): used automatically by Claude Desktop, Cursor, and other MCP clients that support it. No manual token management needed. The OAuth flow creates aPersonal Access Tokenin your profile automatically. Access can be revoked at any time.
Personal Access Token (PAT): for CI/CD, scripts, or clients that don't support OAuth. Create one in your profile underPersonal Access Tokens. Pass it asAuthorization: Bearer lz_pat_.... See thePAT documentationfor details on scopes and security.
The MCP server exposes 26 tools organized by workflow:
These read-only tools give an agent the same context a human translator has, so it can translate, review, and lint in your IDE.
Once connected, you can ask your AI assistant things like:
- "Find all missing German translations in the checkout namespace"
- "Publish the latest version of my project"
- "Add Japanese to all versions"
- "Create a branch for the v2 feature, translate it, then merge it back"
- "Show me which keys changed in English this week"
- "Report these new keys from my codebase to Locize"
- "What's the translation coverage for the production version?"
- "Translate these new strings using the project's glossary and style guide"
- "Lint this PR's new English strings for any forbidden glossary terms"
- "Show me the screenshot where thecheckout.titlekey appears"
To make your AI agent use these tools by default — fetch the glossary and style guide before translating, reuse translation memory, and lint pull requests for forbidden terms — drop our ready-made convention files (CLAUDE.md,AGENTS.md,.cursorrules) into your repo. They live in the publiclocize/locize-agentsrepository.
Tools require specificPAT scopes. If a tool returns a scope error, your token needs additional permissions.
PAT scopes are only the first gate. Your project-levelrole and permissionsstill apply on top:
- Project role: your role on a given project (admin / manager / publisher / user / accountant) always wins when it is stricter than the PAT scope. For example, a PAT withmanagescope called by a user whose project role isreadonlystill cannot modify that project.
- Language / version / namespace scope: if your membership is restricted to specific languages, versions, or namespaces,get_translationsandfind_missing_translationswill reject requests outside that scope.
- translateOnlyusers: the structural tools (add_language,remove_language,change_languages,add_version,delete_version,publish_version,copy_version,copy_language,create_branch,merge_branch,rename_namespace,delete_namespace) are blocked for users marked translate-only.
- Structural changes:add_language,remove_language,change_languages,add_version,delete_version,rename_namespace,delete_namespaceand copying into anewversion need the admin or manager rolewithouta version, language or namespace restriction, exactly like the dashboard.merge_branchneeds the admin or manager role;publish_version,copy_versionandcopy_languageare open to publishers as well, inside their restriction.
- Blocked / revoked access: if your project membership is blocked or your PAT has been revoked, every tool call fails immediately with a 401.
- Parent project access: for tenant and branch projects, merging translations with the parent only happens if your PAT also has access to the parent project; otherwise you see the child-only view.
- Transport:Streamable HTTP (Web StandardRequest/Response)
- Auth:OAuth 2.0 (Authorization Code + PKCE with Dynamic Client Registration) or PAT Bearer token
- Endpoint:POST https://mcp.locize.app
- OAuth metadata:GET https://mcp.locize.app/.well-known/oauth-protected-resource
- Stateless:Each request creates a fresh MCP server instance. No session management required.
- Why not just use AI to translate?: how Locize and AI tools complement each other
- Automatic Translation: combine saveMissing with AI auto-translation for a fully automated workflow
- Personal Access Tokens: create and manage tokens for MCP authentication
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
A MCP server for SimpleLocalize, a translation management system. Requires a SimpleLocalize API key.
Localization as code — 7 MCP tools to push, pull, translate, extract strings, and search translations. AI-powered, type-safe, 182 languages.
Manage content on the microCMS headless CMS using its content and management APIs.
Manage, version, and publish LLM prompts via PromptOT. Build structured prompts from blocks, add variables, save drafts, publish versions, and deliver via API — all from chat.
Manage your app’s translations directly from your AI coding assistant. Search keys, create translations, trigger machine translation. All without leaving your editor.
Translate JSON i18n files using Google Gemini or local Ollama models, with incremental caching support.
65+ AI tools as an MCP server. Research, write, code, scrape, translate, analyze, agent memory, workflows. Pay per call from $0.006.
Integrate Hygraph directly into MCP-compatible tools like Claude and Cursor, executing content operations via natural language
Schedule Once. Post Everywhere. Via MCP, API, or dashboard.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
