English Français العربية

globalize.now

Official registry Developer tools

Localize apps from your AI assistant: translate locale files, set glossaries, connect GitHub repos.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http globalize-now 'https://api.globalize.now/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "globalize-now": {
            "type": "http",
            "url": "https://api.globalize.now/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. globalize.now plugin
  2. What you get
  3. Setup
  4. Example prompts
  5. Scope
  6. Links
  7. License

globalize.now plugin

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:

AreaTools
Projectslist_projects, get_project, create_project, set_project_context
Languageslist_languages, add_project_language, remove_project_language
Translationtranslate_files, get_translation
Glossarylist_glossary, add_glossary_entries, delete_glossary_entry
Style guideslist_style_guides, set_style_guide, delete_style_guide
GitHublist_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.

Setup

  1. Install the plugin.
  2. The first tool call opens a browser window to sign in to globalize.now. Approve access and you're connected.
  3. 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.

License

MIT

Frequently asked questions

What is globalize.now?

Localize apps from your AI assistant: translate locale files, set glossaries, connect GitHub repos.

How do I install globalize.now?

It runs as a remote server. In Claude Code: claude mcp add --transport http globalize-now 'https://api.globalize.now/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does globalize.now need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is globalize.now open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains globalize.now?

It is published by globalize-now. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.