4,000+ servers built on vurb.ts
Vinkius
CursorIDE
Weblate MCP Server

Bring Translation Management
to Cursor

Learn how to connect Weblate to Cursor and start using 32 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add Group AdminsAdd Group RolesCreate GroupCreate LanguageCreate ProjectCreate Project ComponentCreate RoleCreate UserDelete UserGet GroupGet LanguageGet Language StatisticsGet ProjectGet Project File UrlGet Project RepositoryGet RoleGet RootGet UserGet User ContributionsGet User StatisticsList GroupsList LanguagesList Project ComponentsList Project LabelsList Project LanguagesList ProjectsList RolesList User NotificationsList UsersManage User NotificationsPerform Repository OperationUpdate User

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Weblate

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

  1. Subscribe to this server
  2. Enter your Weblate Instance URL and Personal API Token
  3. 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_group_admins

Add team administrators to a group

add_group_roles

Associate roles with a group

create_group

Create a new group

create_language

Create a new language definition

create_project

Create a new project

create_project_component

Create a new component in a project

create_role

Create a new role with specific permissions

create_user

Create a new Weblate user

delete_user

Delete a user (marks inactive)

get_group

Get group details (roles, projects, components)

get_language

Get language details (plural formulas, aliases)

get_language_statistics

Global statistics for a language

get_project

Get project details

get_project_file_url

Get the URL to download all translations as a ZIP archive

get_project_repository

Overall VCS status for the project

get_role

Get role details and permission codenames

get_root

Get Weblate API root entry point

get_user

Get detailed user information

get_user_contributions

List translations with user contributions

get_user_statistics

Get user translation statistics

list_groups

List Weblate groups

list_languages

List all languages

list_project_components

List components within a project

list_project_labels

Manage project labels

list_project_languages

Paginated statistics for all languages in a project

list_projects

List all projects

list_roles

List roles associated with the user

list_user_notifications

List user notification subscriptions

list_users

Requires management permissions or returns self. List Weblate users

manage_user_notifications

Manage user notification subscriptions

perform_repository_operation

Perform VCS operations (push, pull, commit, reset, cleanup)

update_user

Update user details

Why Cursor?

Cursor's Agent mode turns Weblate into an in-editor superpower. Ask Cursor to generate code using live data from Weblate and it fetches, processes, and writes. all in a single agentic loop. 32 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

  • Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

  • Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

  • MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

  • VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

Weblate in Cursor

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Weblate and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Weblate to Cursor 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Weblate in Cursor

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 Cursor 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.

Weblate
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Weblate for Cursor

Every tool call from Cursor to the Weblate MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

05

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

06

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

07

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

08

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

09

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Explore More MCP Servers

View all →