Localize.io

io.localizePublished by localize.ioOfficial publisherv1.0.2Updated Oct 24, 2026

AI localization for agents: translation, TMS sync, translation memories, glossaries, post-editing.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Lets an assistant translate content and work with localization projects, translation memories, glossaries and post-editing through Localize.io.

What you can do
Localize.io is a remote MCP endpoint for AI-driven localization. According to its description, it covers translation, synchronization with a translation management system, translation memories, glossaries and post-editing. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Useful when an assistant should translate or localize content and keep it aligned with an existing translation management system, shared glossaries and translation memories, or when post-editing of machine translations is part of the workflow.
Requirements
A remote streamable HTTP endpoint at hub.localize.io, reachable over the network. Authentication is required: a Localize.io API key sent as a bearer token in the Authorization header, created in the app under Settings, API Keys. No local runtime or packages are needed.
Before you install
The server requires an API key passed in the Authorization header; treat it as a secret and avoid exposing it in logs or shared configuration. The description mentions synchronization with a translation management system, which may write or change translation data in your Localize.io account. Tool-level details are not published in the manifest, so review what it can modify before connecting.

Installation

In SourceWeft

  1. Open Localize.io in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.localize%2Flocalize-io/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "localize-io": {
      "type": "http",
      "url": "https://hub.localize.io/mcp/",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Localize integrations