Atlassian MCP Server vs Weblate MCP
A side-by-side look at the Atlassian MCP Server and Weblate MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Atlassian MCP Server for version control work over a hosted endpoint; choose Weblate MCP for translation services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Atlassian MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
Choose Weblate MCP when
- You need dedicated capabilities in the Translation Services domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
WEBLATE_API_URL, WEBLATE_API_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Translation Services |
| Quality signal | 80/100 · Excellent | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | other | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | WEBLATE_API_URLWEBLATE_API_TOKEN |
| Verified owner | Verified | Community listing |
| GitHub stars | 1,109 | 23 |
| Directory activity | 9 views 0 installs 1 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Atlassian MCP Server | View Weblate MCP |
Tools & capabilities
Atlassian MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Weblate MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Atlassian MCP Server
{
"mcpServers": {
"atlassian-mcp-server": {
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
Weblate MCP
{
"mcpServers": {
"mmntm-weblate-mcp": {
"command": "npx",
"args": [
"-y",
"-",
"no"
],
"env": {
"WEBLATE_API_URL": "YOUR_WEBLATE_API_URL_HERE",
"WEBLATE_API_TOKEN": "YOUR_WEBLATE_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Atlassian MCP Server is categorized under Version Control and uses a remote HTTP/SSE transport. Weblate MCP belongs to Translation Services and uses a local stdio subprocess. Pick Atlassian MCP Server for version control work and Weblate MCP for translation services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Atlassian MCP Server is listed as free. Auth: other. Weblate MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add atlassian-mcp-server and mmntm-weblate-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Atlassian MCP Server has a quality signal of 80/100 (Excellent) with 9 views, 0 installs and 1,109 GitHub stars. Weblate MCP has 59/100 (Good) with 3 views, 0 installs and 23 GitHub stars.