Weblate MCP Server is a Model Context Protocol (MCP) server designed to seamlessly integrate AI assistants with the Weblate translation management platform. It serves as a bridge between AI assistants (such as Claude Desktop) and Weblate instances, enabling users to interact directly with translation projects through natural language without manually navigating the Weblate web interface.
Main capabilities:
- Full Weblate API access: comprehensive integration with the Weblate REST API.
- AI-driven workflows: interact with translation projects using natural language.
- Project management: create, list, and manage translation projects.
- Component operations: handle translation components and configuration.
- Translation management: update, search, and manage translations.
- Language support: supports all languages supported in the Weblate instance.
- Multiple transport methods: HTTP/SSE, Streamable HTTP, and STDIO.
- Type safety: full TypeScript implementation with comprehensive error handling.
- Optimized for LLMs: tool design guides AI models to use them efficiently.
Usage: Using npx is recommended, with no installation required. It can be configured in Claude Desktop or other MCP clients, and also supports development setup. Manual testing, local development, and other scenarios each have corresponding methods. The development environment requires the pnpm package manager and a Weblate instance with API access permissions; the server runs by default on http://localhost:3001。环境变量用于配置，MCP Client configuration includes Claude Desktop (npx or development/local method) as well as HTTP clients (Cursor, VS Code, web applications).
Available tools cover:
- Project management
- Component management
- Translation management (the searchUnitsWithFilters tool uses Weblate's native filtering syntax to efficiently find translations, for example state:=0 to find untranslated strings, state:=10 to find strings needing editing, source:"login" to find strings containing login, component:common AND state:=0 for complex filtering)
- Language management
- Translation statistics dashboard
- Change tracking and history
Architecture tech stack: NestJS, TypeScript, Weblate REST API, MCP protocol, Axios. Development setup includes adding new tools, implementing the MCP tool interface, adding service providers, and updating documentation.
Applicable scenarios:
- Translation management: project supervision, content updates, quality assurance, team coordination.
- Development integration: CI/CD pipelines, content management, localization testing, documentation and statistics reporting.
- AI-assisted workflows: natural language queries, contextual operations, batch operations, intelligent suggestions.
Security and production: API Token security (using environment variables), rate limiting, error handling, input validation (Zod schemas), HTTPS support.
Information such as contribution guidelines and the MIT License is provided.
Limitations: Official materials do not provide specific charging or pricing information; it is not currently available. Other unmentioned feature details are also not currently available.
