Weblate MCP vs Server Everything
A side-by-side look at the Weblate MCP and Server Everything MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Weblate MCP for translation services work as a local process; choose Server Everything for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Translation Services | Other Tools and Integrations |
| Quality signal | 59/100 · Good | 73/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Free | Free |
| Required env vars | WEBLATE_API_URLWEBLATE_API_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 23 | 91,405 |
| Directory activity | 3 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | Not listed | 9 |
| Full listing | View Weblate MCP | View Server Everything |
Tools & capabilities
Weblate MCP tools
No tool names declared yet. Check the project README from the listing page.
Server Everything tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
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.
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"
}
}
}
}
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
Frequently asked questions
Weblate MCP is categorized under Translation Services and uses a local stdio subprocess. Server Everything belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Weblate MCP for translation services work and Server Everything for other tools and integrations.
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.
Weblate MCP is listed as free. Auth: api key required. Server Everything is listed as free. Auth: no auth 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 mmntm-weblate-mcp and modelcontextprotocol-server-everything as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Weblate MCP has a quality signal of 59/100 (Good) with 3 views, 0 installs and 23 GitHub stars. Server Everything has 73/100 (Great) with 9 views, 0 installs and 91,405 GitHub stars.