Skip to main content
Glama
Sign In
globalize-now/globalize

globalize-now/globalize

by globalize-now
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

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:

Area

Tools

Projects

list_projects, get_project, create_project, set_project_context

Languages

list_languages, add_project_language, remove_project_language

Translation

translate_files, get_translation

Glossary

list_glossary, add_glossary_entries, delete_glossary_entry

Style guides

list_style_guides, set_style_guide, delete_style_guide

GitHub

list_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.

Related MCP server: i1n

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

This server cannot be deployed

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Maintenance

ActivitySlowing
ResponsivenessNo recent community issues

Resources

Related MCP Connectors

Related MCP Servers

  • i18n Agent

    kwunlokng
    A
    license
    Not graded
    quality
    D
    maintenance
    AI-powered translation management built for AI agents. Automate localization with regional sensitivity and zero TMS overhead. Works with Claude Code, Cursor, VS Code via MCP protocol. Supports JSON, YAML, Markdown, PO and more.
    7 npm
    MIT

  • Localship

    jigarfumakiya
    A
    license
    Not graded
    quality
    B
    maintenance
    Lets a coding agent find, translate, validate and review an app's existing localization files (Android strings.xml, Apple String Catalogs, gettext) directly in the repo, supplying code usage, comments, glossary and voice notes as context. Placeholders, plural forms, escaping and markup are checked in code before any translation is written, and results land as reviewable drafts that never overwrite hand edits or approved work.
    28 npm
    1
    MIT

  • verbaly

    AronSoto
    A
    license
    A
    quality
    A
    maintenance
    The i18n cycle of a JavaScript project as tools: extract the texts written in code, list missing translations and write machine translations as drafts that a person approves. Works with React, Vue, Svelte, Next.js, Nuxt, SvelteKit and Astro.
    9
    4
    MIT