Allows connecting a GitHub repository to a localization project, detecting repositories, listing branches, and setting path patterns so translations are delivered as locale files in the repository.
Provides localization infrastructure for Next.js apps, including project management, language management, translation of locale files, glossary and style guide consistency, and GitHub integration to sync translations into repositories.
Provides localization infrastructure for React apps, including project management, language management, translation of locale files, glossary and style guide consistency, and GitHub integration to sync translations into repositories.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@globalize-now/globalize Show my globalize.now projects and their target languages"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
|
Languages |
|
Translation |
|
Glossary |
|
Style guides |
|
GitHub |
|
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.
Related MCP server: Verblaze MCP Server
Install the plugin.
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.
"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"
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.
Website: https://globalize.now/en/developers/
Documentation: https://help.globalize.now
Privacy: https://globalize.now/en/privacy/
Support: support@globalize.now
MIT
This server cannot be deployed
AI localization for agents: translation, TMS sync, translation memories, glossaries, post-editing.
Manage translation projects, phrases and locales with secure organization-scoped tools and views.
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Manage product translations from Claude and ship reviewed changes as GitHub pull requests.
