Home Using globalize.now Connect an AI agent with the Globalize MCP server

Connect an AI agent with the Globalize MCP server

Last updated on Jul 10, 2026

The Globalize MCP server lets an AI agent — Claude, Claude Code, Cursor, or any MCP-compatible client — work with your localization directly: create projects, add languages, translate files, and connect a GitHub repo, all from inside the tool you already use. A connected agent acts on your behalf, with your own permissions.

The server endpoint is:

https://api.globalize.now/mcp

Pick your setup

Claude.ai, ChatGPT, or any client with OAuth

  1. Add Globalize as a custom connector using the URL above.
  2. Sign in with your Globalize account when the client prompts you. No API key needed.
  3. Tool calls run as you, in the organisation you last used in the dashboard.

Claude Code

Run this in your terminal, then run /mcp inside Claude Code and sign in through your browser:

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

Cursor

Add this to ~/.cursor/mcp.json. Cursor prompts you to sign in on first use:

{
  "mcpServers": {
    "globalize": {
      "url": "https://api.globalize.now/mcp"
    }
  }
}

Any other MCP client

Generate an API key on the MCP page in your dashboard (it's shown once), then configure a Streamable HTTP transport pointed at the endpoint with the header Authorization: Bearer <your key>.

What the agent can do once connected

  • Set up projects — create a project, add or remove target languages, set project-wide context.
  • Connect your repository — link a GitHub repo, detect its framework and locale file patterns, and keep translations in sync on every push.
  • Translate files — hand the agent a locale file (JSON, ARB, PO, XLIFF, YAML, Android XML, or iOS .xcstrings) and get the translated versions back.
  • Keep quality consistent — manage a glossary and per-language style guides.

What it does not do

The MCP server does not internationalize your source code. It works on locale files, not your components. To turn hardcoded strings into translation keys, use the Globalize skills in your coding agent. If your agent is connected to the MCP, install them in one step by running the install-skills prompt (a slash command) instead of running npx skills add globalize-now/globalize-skills yourself. See "MCP, CLI, or skills — which one do I need?"

Revoking access

Remove the connector in your client, and revoke any API key from Settings → Manage keys in the dashboard.