MCP Local Rag vs Shipi18n
A side-by-side look at the MCP Local Rag and Shipi18n MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Local Rag for knowledge & memory work as a local process; choose Shipi18n 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 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, BASE_DIRS, IGNORE_PATHS, DB_PATH, CACHE_DIR, HF_ENDPOINT. - You want tools like
sync_start, sync_status, ingest_file.
Choose Shipi18n when
- You need dedicated capabilities in the Translation Services domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Translation Services |
| Quality signal | 69/100 · Great | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | BASE_DIRBASE_DIRSIGNORE_PATHSDB_PATHCACHE_DIRHF_ENDPOINT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 416 | 0 |
| Directory activity | 13 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View MCP Local Rag | View Shipi18n |
Tools & capabilities
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
Shipi18n 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.
MCP Local Rag
{
"mcpServers": {
"shinpr-mcp-local-rag": {
"command": "npx",
"args": [
"-y",
"mcp-local-rag"
],
"env": {
"BASE_DIR": "YOUR_BASE_DIR_HERE",
"BASE_DIRS": "YOUR_BASE_DIRS_HERE",
"IGNORE_PATHS": "YOUR_IGNORE_PATHS_HERE",
"DB_PATH": "YOUR_DB_PATH_HERE",
"CACHE_DIR": "YOUR_CACHE_DIR_HERE",
"HF_ENDPOINT": "YOUR_HF_ENDPOINT_HERE"
}
}
}
}
Shipi18n
{
"mcpServers": {
"shipi18n": {
"command": "npx",
"args": [
"-y",
"@shipi18n/cli"
]
}
}
}
Frequently asked questions
MCP Local Rag is categorized under Knowledge & Memory and uses a local stdio subprocess. Shipi18n belongs to Translation Services and uses a local stdio subprocess. Pick MCP Local Rag for knowledge & memory work and Shipi18n 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.
MCP Local Rag is listed as free. Auth: no auth required. Shipi18n 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 shinpr-mcp-local-rag and shipi18n as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Local Rag has a quality signal of 69/100 (Great) with 13 views, 0 installs and 416 GitHub stars. Shipi18n has 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.