mcpField
G
globalize.now

globalize.now

Remote
globalize.nowDeveloper Tools0Updated 5w ago

About globalize.now

The globalize.now plugin provides localization management for React, Next.js, and Vue projects, for developers handling translations from an editor or agent workflow. It manages languages, glossaries, and style guides, and puts translated files in GitHub repositories.

Key features

  1. 01Manage projects and target languages
  2. 02Submit and retrieve locale translations
  3. 03Maintain glossaries and language style guides
  4. 04Connect GitHub repositories for translations
  5. 05Support multiple localization file formats

Use cases

  1. 01Add or remove target languages for an app
  2. 02Translate JSON, PO, or XLIFF files
  3. 03Keep terminology and style consistent across languages
  4. 04Place translated files in a GitHub repository

MCP support

The remote MCP server at `https://api.globalize.now/mcp` exposes 21 tools for managing projects, languages, translations, glossaries, style guides, and GitHub connections.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.globalize.now/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

globalize.now plugin

smithery badge

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.