Official description๐ โ๏ธ ๐ ๐ ๐ช ๐ง - MapRag: RAG-focused MCP subregistry for discovering and routing to retrieval-capable MCP servers with structured constraints and explainable ranking.
Config template (adjust for your client)
claude mcp add ragmap -- npx -y ragmap
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
6 โ ยท khalidsaidi/ragmap ยท read from the repository page ยท (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list ยท type: MCP server
Harvest history
first seen 2026-10-09 ยท last seen 2026-10-16 ยท seen 32ร ยท listed by 7 sources
Score
score 703 ยท 6 โ ยท 7 sources ยท mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP ๆๅก. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository khalidsaidi/ragmap๏ผfirst catalogued 2026-10-09๏ผlast seen 2026-10-16ใThere is no official certification or quality rating here โ we record sources and dates only.
**Try it:** https://ragmap-api.web.app/browse/ **Start here:** https://github.com/khalidsaidi/ragmap/discussions/17 RAGMap is a lightweight MCP Registry-compatible subregistry + MCP server focused on **RAG-related MCP servers**. It: - Ingests the official MCP Registry, enriches records for RAG use-cases, and serves a subregistry API. - Exposes an MCP server (remote Streamable HTTP + local stdio) so agents can search/filter RAG MCP servers. MapRag (RAGMap) **MapRag is a discovery + routing layer for retrieval.** It helps agents and humans answer: *which retrieval MCP server should I use for this task, given my constraints?* RAGMap does **not** do retrieval itself. It indexes and enriches retrieval-capable servers, then routes you to the right tool/server. What you get after install (plain English) - You get **discovery/routing tools** (rag_find_servers, rag_get_server, rag_list_categories, rag_explain_score). - RAGMap helps you find the best retrieval server for your task and constraints. - Your agent then connects to that chosen server to do the actual retrieval. RAGMap does **not**: - Ingest your private documents automatically. - Host your personal vector database. - Replace your end-to-end RAG pipeline. If you need retrieval over your own data, use a retrieval server from RAGMap results (or your own server) that supports your ingest/index flow. Freshness and ingest - Hosted RAGMap updates its index on a schedule. Newly published/changed servers may appear with some delay. - Most users do **not** run ingest themselves when using the hosted service. - If you need tighter freshness control or private indexing behavior, self-host and run your own ingest schedule (docs/DEPLOYMENT.md). **Features:** Registry-compatible API; **semantic + keyword search** (when OPENAI_API_KEY is set, e.g. from env or your deploymentโs secret manager); categories and ragScore; filter by **hasRemote**, **reachable** (probe-checked for streamable-http/SSE), **citations**, **localOnly**, transport, minScore, categories. **Human browse UI** at ragmap-api.web.app/browse โ search, filter, copy Cursor/Claude config. MCP tools: rag_find_servers, rag_get_server, rag_list_categories, rag_explain_score. Quickstart > Requirements: curl and jq 1) Top reachable retrievers (checked within 24h) 2) Search with trust filter (reachable recently) 3) Get install config for a server Tip: URL-encode names that contain /. 4) Inspect freshness and coverage 5) Usage telemetry summary Full overview: docs/OVERVIEW.md Release history: CHANGELOG.md Architecture Mermaid source Monorepo layout - apps/api: REST API + MCP registry-compatible endpoints + ingestion worker - apps/mcp-remote: Remote MCP server (Streamable HTTP) - packages/mcp-local: Local MCP server (stdio) - packages/shared: Zod schemas + shared types - docs: docs + Firebase Hosting static assets Local dev Optional: set OPENAI_API_KEY in .env (see .env.example) to enable **semantic search** locally; GET /health will show "embeddings": true.