Filesystem vs Weblate MCP
A side-by-side look at the Filesystem 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 Filesystem for file systems work as a local process; 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 Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
path, head, tail.
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 | File Systems | Translation Services |
| Quality signal | 85/100 · Excellent | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | WEBLATE_API_URLWEBLATE_API_TOKEN |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,512 | 23 |
| Directory activity | 9 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 17 | Not listed |
| Full listing | View Filesystem | View Weblate MCP |
Tools & capabilities
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 more on 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.
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
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
Filesystem is categorized under File Systems and uses a local stdio subprocess. Weblate MCP belongs to Translation Services and uses a local stdio subprocess. Pick Filesystem for file systems 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.
Filesystem is listed as free. Auth: no auth required. 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 filesystem and mmntm-weblate-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Filesystem has a quality signal of 85/100 (Excellent) with 9 views, 0 installs and 91,512 GitHub stars. Weblate MCP has 59/100 (Good) with 3 views, 0 installs and 23 GitHub stars.