← Registry

Developer Tools

locize.com

A platform for managing localization and translation workflows, bridging development and translation teams.

1 endpoint0 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://mcp.locize.app

No auth detected

Known tools 0

No tool metadata was available in the registry cache.

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.locize-com]
url = "https://mcp.locize.app"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "locize-com": {
      "type": "http",
      "url": "https://mcp.locize.app"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: locize-com
Remote MCP URL: https://mcp.locize.app

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "locize-com": {
      "url": "https://mcp.locize.app"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "locize-com": {
      "type": "http",
      "url": "https://mcp.locize.app"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "locize-com",
  "transport": "streamable-http",
  "url": "https://mcp.locize.app"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for locize.app was fetched 2026-08-04T11:23:52.208Z and is being refreshed.

Trust status Trusted

locize.app is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.