globalize.now plugin

MCP serverDev tools

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

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use globalize.now plugin

Install globalize.now plugin

The server’s own address, for the clients that take one directly. Or connect ahel onceand every client you use reads it from one address, with the account kept on ahel rather than in each client’s config.

  • Claude Code

    claude mcp add --transport http globalize-now-plugin 'https://api.globalize.now/mcp'

    Run it once in your project, then open /mcp to approve any sign-in the server asks for.

  • Claude Desktop

    https://api.globalize.now/mcp

    Add a custom connector in Settings, paste this address, and approve the sign-in.

  • Cursor

    cursor://anysphere.cursor-deeplink/mcp/install?name=globalize-now-plugin&config=eyJ1cmwiOiJodHRwczovL2FwaS5nbG9iYWxpemUubm93L21jcCJ9

    Open the link and Cursor adds the server at that address.

  • ChatGPT

    https://api.globalize.now/mcp

    In Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.

  • Codex

    codex mcp add globalize-now-plugin --url 'https://api.globalize.now/mcp'

    Run it once, then sign in with codex mcp login globalize-now-plugin if the server asks for an account.

From the project's README

As published by globalize-now/globalize-plugin in README.md.

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.

Links

License

MIT

Advanced
Delivery
globalize MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
Catalog kind
mcp-server
Gateway key
io-github-globalize-now-globalize
Source
github.com/globalize-now/globalize-plugin
Hosted endpoint
https://api.globalize.now/mcp