Globalize.now vs I18n Agent

A side-by-side look at the Globalize.now and I18n Agent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Globalize.now logoGlobalize.nowTranslation Services · Remote HTTP/SSELocalize apps from your AI assistant: translate locale files, set glossaries, connect GitHub repos.40FairAuth: not declaredI18n Agent logoI18n AgentTranslation Services · Local subprocess (stdio)AI-powered translation for 48 languages with context-aware quality39FairAuth: not declared

Verdict: choose Globalize.now for translation services work over a hosted endpoint; choose I18n Agent for translation services as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Globalize.now logoChoose Globalize.now when

  • You need dedicated capabilities in the Translation Services domain.
  • You prefer a remote HTTP/SSE transport.
Explore Globalize.now

I18n Agent logoChoose I18n Agent when

  • You need dedicated capabilities in the Translation Services domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: I18N_AGENT_API_KEY, MCP_SERVER_URL.
Explore I18n Agent

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGlobalize.now logoGlobalize.nowI18n Agent logoI18n Agent
CategoryTranslation ServicesTranslation Services
Quality signal40/100 · Fair39/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedI18N_AGENT_API_KEYMCP_SERVER_URL
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Globalize.now tools

No tool names declared yet. Check the project README from the listing page.

I18n Agent tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Globalize.now

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "globalize-now": {
      "url": "https://api.globalize.now/mcp"
    }
  }
}

I18n Agent

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "i18n-agent": {
      "command": "npx",
      "args": [
        "-y",
        "@i18n-agent/mcp-client"
      ],
      "env": {
        "I18N_AGENT_API_KEY": "YOUR_I18N_AGENT_API_KEY_HERE",
        "MCP_SERVER_URL": "YOUR_MCP_SERVER_URL_HERE"
      }
    }
  }
}

Frequently asked questions

Globalize.now is categorized under Translation Services and uses a remote HTTP/SSE transport. I18n Agent belongs to Translation Services and uses a local stdio subprocess. Pick Globalize.now for translation services work and I18n Agent for translation services.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Globalize.now has no declared pricing — check the project's own site. I18n Agent has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add globalize-now and i18n-agent as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Globalize.now has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. I18n Agent has 39/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.