Localize apps from your AI assistant: translate locale files, set glossaries, connect GitHub repos.
Model Context Protocol (MCP) Server: io.github.globalize-now/globalize
This MCP server provides localization for AI agents, including projects, languages, glossaries, and translations. It is described as “Localization for AI agents,” with the scope focused on organizing and retrieving localized content for agent workflows.
🛠️ Key Features
Localization for AI agents
Projects
Languages
Glossaries
Translations
🚀 Use Cases
Managing multiple languages for AI agent content
Organizing agent localization projects
Maintaining glossaries for consistent terminology
Converting source content into translated versions
⚡ Developer Benefits
Structured access to localization elements (projects, languages, glossaries, translations)
⚠️ Limitations
No additional capabilities, tooling, or constraints are provided in the available source data.
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.
What you get
A remote MCP server (https://api.globalize.now/mcp) exposing 21 tools:
The first tool call opens a browser window to sign in to globalize.now. Approve access and you're connected.
No API key, no config file. Authentication is OAuth against your own globalize.now account.
A globalize.now account is required (sign up free). Translation jobs consume account credits.
Example prompts
"Show my globalize.now projects and their target languages"
"Add Japanese to my storefront project"
"Translate these locale files into German and French and show me the result"
"Add a glossary entry so 'Pro Plan' is never translated"
"Connect my GitHub repo and use locales/{locale}/{namespace}.json as the path pattern"
Scope
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.