Log inSubmit server
Weblate MCP logo

Weblate MCP

by mmntm

Manage Weblate projects, components, translations, languages, statistics, and change history through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Weblate MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mmntm-weblate-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "-",
        "no"
      ],
      "env": {
        "WEBLATE_API_URL": "YOUR_VALUE_HERE",
        "WEBLATE_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command didn't complete successfully in our automated test.

npx -y - no

npm ERR! could not determine executable to run npm ERR! A complete log of this run can be found in: /home/user/.npm/_logs/2026-09-26T11_17_23_960Z-debug-0.log

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

Weblate translation projects can be managed through the mmntm/weblate-mcp MCP server, which connects MCP clients to Weblate's REST API. It provides tools for project and component management, translation lookup and updates, language discovery, statistics, and change tracking. The server supports STDIO, HTTP/SSE, and Streamable HTTP transports, with Weblate URL and API token configuration. Reach for it when an AI assistant needs to inspect or modify translation data in a Weblate instance.

Use cases

  • List Weblate projects and components
  • Search for untranslated strings with filters
  • Update translations for selected languages
  • Review translation progress and statistics
  • Inspect recent translation changes

Key features

  • Weblate REST API access through MCP
  • Project and component management
  • Filtered translation search
  • Single and bulk translation updates
  • Translation and contribution statistics
  • Change-history queries

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

18/19 checks healthy over the last 86d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · no (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars24Stargazers on the source repository.
npm downloads2.8kPackage downloads in the last 30 days.
Last commit20d agoMost recent push to the default branch.
Install checkInconclusiveInstall command did not finish in our automated test.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Weblate MCP works

What mmntm/weblate-mcp MCP server does

The mmntm/weblate-mcp MCP server exposes Weblate translation management through the Model Context Protocol. It lets an MCP client query projects, components, languages, translation units, statistics, and recent activity without requiring the assistant to navigate Weblate's web interface directly.

Supported workflows include listing projects and their components, finding translations by key or text, reading a translation for a specific key, and writing one or many translation values. Project and component statistics provide completion and string-count information, while language and user statistics support broader progress and contribution analysis. Change-history tools can filter recent activity by project, component, or user.

How it works

The server acts as an MCP-facing layer over Weblate's REST API. An MCP client sends tool calls to the server, and the server uses the configured Weblate instance and API token to perform the corresponding operation. Results are returned to the client for use in an assistant conversation or an automation workflow.

Three transport options are described: STDIO for local MCP client integrations, HTTP/SSE, and Streamable HTTP. The development server uses port 3001 by default and exposes an HTTP MCP endpoint at /mcp when configured for HTTP access.

For translation discovery, searchUnitsWithFilters uses Weblate's native filtering syntax. This supports queries such as finding untranslated strings with state:=0, locating text containing a term with source:"login", or combining a component and state condition. This approach is intended to avoid fetching every key and checking entries individually.

Setup and configuration

The mmntm/weblate-mcp MCP server requires Node.js 18 or newer for the documented development setup, along with access to a Weblate instance and its API. The published package can be launched with npx:

Terminal
npx -y @mmntm/weblate-mcp

Configure the MCP client with these environment variables:

  • WEBLATE_API_URL: the Weblate API base URL.
  • WEBLATE_API_TOKEN: the API token used to access Weblate.

The development workflow uses pnpm to install dependencies, build the TypeScript project, and start the server. Optional runtime settings shown in the documentation include PORT, NODE_ENV, and LOG_LEVEL.

Claude Desktop can run the server through the npx command and environment configuration. HTTP clients such as Cursor can connect to a locally running endpoint using http://localhost:3001/mcp.

Tools and capabilities

Available tool groups cover:

  • Project listing and project management.
  • Component listing and configuration details.
  • Translation search, lookup, updates, and bulk writes.
  • Language listing for a project.
  • Project, component, translation, language, and user statistics.
  • Recent changes across projects or filtered by project, component, or user.

The documented tool list includes listProjects, listComponents, searchUnitsWithFilters, searchStringInProject, getTranslationForKey, writeTranslation, bulkWriteTranslations, findTranslationsForKey, and several statistics and history tools. Write operations can update translation values, and the write tool includes approval support.

Limitations and notes

HTTP client setup assumes that the server is running locally or is otherwise reachable at the configured MCP URL.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Weblate MCP

Run `npx -y @mmntm/weblate-mcp`, then configure the server with `WEBLATE_API_URL` and `WEBLATE_API_TOKEN`.

Yes. The README provides Claude Desktop configuration using npx and the Weblate API environment variables.

It requires `WEBLATE_API_URL` for the Weblate API endpoint and `WEBLATE_API_TOKEN` for API authentication.

Yes. The documented `bulkWriteTranslations` tool supports batch updates with error handling.

Configure Cursor or another HTTP MCP client to use the server endpoint, documented as `http://localhost:3001/mcp` for a local server.

Related MCP servers

All in Translation Services All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWeblate MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mmntm-weblate-mcp?style=directory)](https://allmcps.com/mcp/mmntm-weblate-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/mmntm-weblate-mcp"><img src="https://allmcps.com/api/badge/mmntm-weblate-mcp?style=directory" alt="Weblate MCP on AllMCPs" /></a>