Polytranslator vs MCP Local Rag
A side-by-side look at the Polytranslator and MCP Local Rag MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Polytranslator for translation services work over a hosted endpoint; choose MCP Local Rag for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Polytranslator when
- You need dedicated capabilities in the Translation Services domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
POLYTRANSLATOR_API_KEY.
Choose MCP Local Rag when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
BASE_DIR. - You want tools like
sync_start, sync_status, ingest_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Translation Services | Knowledge & Memory |
| Quality signal | 40/100 · Fair | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | POLYTRANSLATOR_API_KEY | BASE_DIR |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 415 |
| Directory activity | 1 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | Not listed | 9 |
| Full listing | View Polytranslator | View MCP Local Rag |
Tools & capabilities
Polytranslator tools
No tool names declared yet. Check the project README from the listing page.
MCP Local Rag tools 9
sync_startReconcile the index with all configured roots or one pathsync_statusPoll a running sync jobingest_fileIngest or replace one fileingest_dataIngest text, Markdown, or HTML already held by the clientquery_documentsSearch with semantic matching and keyword boostread_chunk_neighborsRead surrounding chunks from a search resultlist_filesShow supported files and their ingestion statedelete_fileDelete an indexed file or an `ingest_data` itemstatusShow index and search status
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.
Polytranslator
{
"mcpServers": {
"polytranslator": {
"url": "https://www.polytranslator.com/api/mcp"
}
}
}
MCP Local Rag
{
"mcpServers": {
"shinpr-mcp-local-rag": {
"command": "npx",
"args": [
"-y",
"mcp-local-rag"
],
"env": {
"BASE_DIR": "YOUR_BASE_DIR_HERE"
}
}
}
}
Frequently asked questions
Polytranslator is categorized under Translation Services and uses a remote HTTP/SSE transport. MCP Local Rag belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Polytranslator for translation services work and MCP Local Rag for knowledge & memory.
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.
Polytranslator has no declared pricing — check the project's own site. MCP Local Rag 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 polytranslator and shinpr-mcp-local-rag as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Polytranslator has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. MCP Local Rag has 69/100 (Great) with 9 views, 0 installs and 415 GitHub stars.