Log inSubmit server

Globalize.now vs Translation AI MCP

A side-by-side look at the Globalize.now and Translation AI MCP 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 declaredTranslation AI MCP logoTranslation AI MCPTranslation Services · Local subprocess (stdio)Translation Ai automation via MCP. Includes translate text, detect language, check grammar. By MEOK41FairAuth: not declared

Verdict: choose Globalize.now for translation services work over a hosted endpoint; choose Translation AI MCP 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

Translation AI MCP logoChoose Translation AI MCP when

  • You need dedicated capabilities in the Translation Services domain.
  • You prefer a local stdio subprocess transport.
Explore Translation AI MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGlobalize.now logoGlobalize.nowTranslation AI MCP logoTranslation AI MCP
CategoryTranslation ServicesTranslation Services
Quality signal40/100 · Fair41/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Globalize.now View Translation AI MCP

Tools & capabilities

Globalize.now tools

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

Translation AI MCP 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"
    }
  }
}

Translation AI MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "translation-ai-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "meok-setup"
      ]
    }
  }
}

Frequently asked questions

Globalize.now is categorized under Translation Services and uses a remote HTTP/SSE transport. Translation AI MCP belongs to Translation Services and uses a local stdio subprocess. Pick Globalize.now for translation services work and Translation AI MCP 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. Translation AI MCP 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 translation-ai-mcp 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. Translation AI MCP has 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.

Popular comparisons with Globalize.now

Popular comparisons with Translation AI MCP