Compatible with every major AI agent and IDE
What is the Weblate MCP Server?
Connect your Weblate instance to any AI agent to streamline your continuous localization and translation management through natural conversation.
What you can do
- Project & Component Management — List all projects, fetch component details, and explore translation files directly from the Weblate API.
- Language Insights — Retrieve detailed statistics for specific languages to track translation progress and identify missing strings.
- User & Group Administration — Manage user profiles, list contributions, and handle group roles or administrative permissions.
- Repository Operations — Perform critical repository actions like pulling updates or pushing translations to keep your version control in sync.
- Notification Control — List and manage user notification subscriptions to stay updated on translation changes.
How it works
- Subscribe to this server
- Enter your Weblate Instance URL and Personal API Token
- Start managing your localization projects from Claude, Cursor, or any MCP-compatible client
No more switching between your IDE and the Weblate dashboard to check translation status or user permissions. Your AI acts as a localization manager.
Who is this for?
- Localization Managers — quickly check project health, language coverage, and user contributions without manual reporting.
- Developers — trigger repository syncs and inspect component structures directly from the code editor.
- DevOps Engineers — automate user provisioning and group role assignments within the localization infrastructure.
Built-in capabilities (32)
Add team administrators to a group
Associate roles with a group
Create a new group
Create a new language definition
Create a new project
Create a new component in a project
Create a new role with specific permissions
Create a new Weblate user
Delete a user (marks inactive)
Get group details (roles, projects, components)
Get language details (plural formulas, aliases)
Global statistics for a language
Get project details
Get the URL to download all translations as a ZIP archive
Overall VCS status for the project
Get role details and permission codenames
Get Weblate API root entry point
Get detailed user information
List translations with user contributions
Get user translation statistics
List Weblate groups
List all languages
List components within a project
Manage project labels
Paginated statistics for all languages in a project
List all projects
List roles associated with the user
List user notification subscriptions
Requires management permissions or returns self. List Weblate users
Manage user notification subscriptions
Perform VCS operations (push, pull, commit, reset, cleanup)
Update user details
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Weblate through native MCP adapters. Connect 32 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Weblate MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Weblate queries for multi-turn workflows
Weblate in LangChain
Weblate and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Weblate to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Weblate in LangChain
The Weblate MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 32 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Weblate for LangChain
Every tool call from LangChain to the Weblate MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check the translation progress for a specific language code?
Yes! Use the get_language_statistics tool with the language code (e.g., 'fr'). The agent will return detailed metrics including translated, fuzzy, and failing strings.
Is it possible to trigger a Git pull or push from the AI?
Absolutely. Use the perform_repository_operation tool. You can specify the project and component along with the operation (like 'pull' or 'push') to sync with your remote repository.
Can I manage user access and view their contributions?
Yes. You can use list_users to see accounts, get_user_contributions to audit translation activity, and add_group_roles to manage permissions programmatically.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
Explore More MCP Servers
View all →
Salesbricks
10 toolsIntegrate Salesbricks seamlessly into your AI. Quickly manage B2B customer billing, track active subscriptions, list available software plans, and audit invoices natively.

Ocoya Social Media
9 toolsManage Ocoya social profiles, posts, workspaces, and workflows.

GitLab
12 toolsManage projects, track issues, and oversee CI/CD pipelines via AI agents with GitLab.

Zoho Invoice
10 toolsManage customers, create invoices, and automate billing on Zoho Invoice — the clean and simple invoicing software for small business.
