Other · Remote MCP server
Locize
Locize TMS: 26 tools for translations, TM/glossary/styleguide/screenshot context, versions. OAuth.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
app.locize.mcp/server- Version
- 2.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-28
- Updated
- 2026-07-28
- Publisher
- app.locize.mcp
- Namespace
- Namespace verified by the MCP Registry via the domain mcp.locize.app or a parent domain of it · how
- Website
- www.locize.com/docs/integration/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.locize.app | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Locize
Locize is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.locize.app, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Localization Resource IntegrityChecks the structural integrity of translated resource dictionaries against a source dictionary y... | Remote · HTTPLive check: ✓ handshake |
| Localize.ioAI localization for agents: translation, TMS sync, translation memories, glossaries, post-editing. | Remote · HTTPLive check: sign-in required |
| LocalKeepLocal chronological memory banks you control; Claude recalls them via MCP. | Local · stdio |
| Loci Labs Real-World ObservationsFresh human-observable information about physical places and conditions that may be stale online. | Remote · HTTPLive check: ✓ handshake |
| LockboxEncrypted secrets for Next.js. AES-256-GCM with no vault needed. | Local · stdio |
| lockdocsExact-version library docs from your lockfile - local, offline, no rate limits. | Local · stdio |
| Lockstep MCPLocal lockfile and package-manager reproducibility analysis without dependency details. Tools... | Local · stdio |
| lockvetExplain any lockfile or workflow-pin change: bumps, vulns, ages, deprecations - 61 formats. | Local · stdio |