Localize apps from your AI assistant: translate locale files, set glossaries, connect GitHub repos.
MCPpedia last refreshed this data
io.github.globalize-now/globalize is an MCP server that localize apps from your AI assistant: translate locale files, set glossaries, connect GitHub repos. Its tool list has not been published yet over http, requires no API key, and scores 66/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
https://api.globalize.now/mcpRemote servers are added as connectors, not in claude_desktop_config.json, which is for local servers.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Localize apps from your AI assistant: translate locale files, set glossaries, connect GitHub repos.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ai-ml / writing
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
An open-source AI agent that brings the power of Gemini directly into your terminal.
🛡️ BLA (Blind LLM Agents) — Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.
Open source device layer for AI agents: control mobile, web, TV, and desktop apps over MCP
MCP Security Weekly
Get CVE alerts and security updates for io.github.globalize-now/globalize and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Localization infrastructure for React, Next.js and Vue apps, usable from your editor or agent.
Connect this plugin and you can run your localization without leaving your workflow: list projects and their target languages, add or remove languages, submit locale files for translation and pull the results back, keep glossaries and per-language style guides consistent, and connect a GitHub repository so translations land in your repo as locale files.
Translations live in your repository, not in a runtime widget.
A remote MCP server (https://api.globalize.now/mcp) exposing 21 tools:
| Area | Tools |
|---|---|
| Projects | list_projects, get_project, create_project, set_project_context |
| Languages | list_languages, add_project_language, remove_project_language |
| Translation | translate_files, get_translation |
| Glossary | list_glossary, add_glossary_entries, delete_glossary_entry |
| Style guides | list_style_guides, set_style_guide, delete_style_guide |
| GitHub | list_github_installations, start_github_install, detect_repository, list_repository_branches, connect_repository, set_repository_patterns |
Supported file formats: JSON (flat, nested, ARB, Chrome messages.json), PO, XLIFF 1.2 and 2.0, YAML, @wxt-dev/i18n TOML/JSON5/JSONC, Android XML, iOS xcstrings, Markdown and HTML.
A globalize.now account is required (sign up free). Translation jobs consume account credits.
This plugin manages localization projects and translation. Converting hardcoded strings in your source code into i18n keys is done by the globalize.now app or the setup skills — see the developer docs.
MIT