Filesystem vs Locize
A side-by-side look at the Filesystem and Locize MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LocizeTranslation Services · Remote HTTP/SSELocize MCP server: read/write translations, publish versions, manage branches from AI assistants.42FairAuth: not declaredVerdict: choose Filesystem for file systems work as a local process; choose Locize for translation services over a hosted endpoint. 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.
LChoose Locize when
- You need dedicated capabilities in the Translation Services domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Locize | |
|---|---|---|
| Category | File Systems | Translation Services |
| Quality signal | 85/100 · Excellent | 42/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,512 | — |
| Directory activity | 9 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 17 | Not listed |
| Full listing | View Filesystem | View Locize |
Tools & capabilities
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 more on the listing page
Locize 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"
]
}
}
}
Locize
{
"mcpServers": {
"locize": {
"url": "https://www.locize.com/docs/integration/mcp"
}
}
}
Frequently asked questions
Filesystem is categorized under File Systems and uses a local stdio subprocess. Locize belongs to Translation Services and uses a remote HTTP/SSE transport. Pick Filesystem for file systems work and Locize 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. Locize has no declared pricing — check the project's own site. 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 locize 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. Locize has 42/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.