retrieval-lens
retrieval-lens
A black-box flight recorder for RAG retrieval inside MCP agents.
retrieval-lens is an MCP server that logs every retrieval step your RAG agent makes — what chunks were retrieved, their scores, sources, and rankings — so you can audit, replay, and diff retrieval runs after the fact.
The Problem
When a RAG agent gives a wrong answer, you need to know: did retrieval fail, or did generation fail? Right now there's no easy way to answer that. Your observability tool shows you the LLM call. It doesn't show you which chunks the model saw before it answered, what scores they had, or how retrieval changed between yesterday and today.
retrieval-lens fixes that. Every retrieval run is logged. Nothing is hidden.
Related MCP server: Graphlit MCP Server
Demo
When your RAG agent gives a wrong answer, ask retrieval-lens what it saw:
await mcp.call("retrieval_diff", {
run_id_a: "support-bot-before-embedding-refresh",
run_id_b: "support-bot-after-embedding-refresh",
match_by: "source"
});See docs/demo-diff.png for real output from Claude Code.
MCP Tools
Tool | What it does |
| Log a retrieval run — query, chunks, scores, sources, rankings |
| Replay what the model saw before a specific answer |
| Compare two retrieval runs — what changed, what score drifted |
| Aggregate score distributions, top sources, runs over time |
Quickstart
Run retrieval-lens directly with npx:
npx retrieval-lensAdd retrieval-lens to Claude Code with one command:
claude mcp add retrieval-lens npx retrieval-lensThen call retrieval_observe after every retrieval step in your RAG pipeline:
await mcp.call("retrieval_observe", {
run_id: crypto.randomUUID(),
query: "what is the refund policy?",
chunks: [
{ content: "Refunds are processed within 5 days...", score: 0.91, source: "policy.md", rank: 1 },
{ content: "Contact support for refund requests...", score: 0.74, source: "faq.md", rank: 2 }
],
pipeline_tag: "support-bot"
});Adapters
LangChain
See examples/langchain-adapter.ts
LlamaIndex
See examples/llamaindex-adapter.ts
Why not LangSmith / Langfuse?
Those are full observability platforms. retrieval-lens is surgical:
Local-first — SQLite, zero signup, no data leaves your machine
MCP-native — one config line, works in any MCP client
Retrieval-only — focused on the layer where most RAG failures actually happen
Status
🚧 Active development. Harness-first build using harness engineering principles.
F05 — scaffold
F01 — retrieval_observe
F02 — retrieval_query
F03 — retrieval_diff
F04 — retrieval_stats
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
AlicenseBqualityCmaintenanceThis repository is an example of how to create a MCP server for Qdrant, a vector search engine.Last updated21,487Apache 2.0
Graphlit MCP Serverofficial
Alicense-qualityDmaintenanceThe Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.Last updated64379MIT
Chroma MCP Serverofficial
AlicenseAqualityDmaintenanceA server that provides data retrieval capabilities powered by Chroma embedding database, enabling AI models to create collections over generated data and user inputs, and retrieve that data using vector search, full text search, and metadata filtering.Last updated13584Apache 2.0- AlicenseAqualityCmaintenanceCognitive prosthetic for AI agents. Indexes conversation history from ChatGPT, Claude Code, Cursor, and Gemini CLI into searchable embeddings. 25 MCP tools including tunnel_state (resume where you left off), switching_cost (quantify context-switch penalty), thinking_trajectory (track idea evolution), and alignment_check (decisions vs principles). LanceDB + Parquet, 12ms recall, local-first.Last updated2565MIT
Related MCP Connectors
Agent Replay Debugger MCP — record every agent step + deterministic replay. Step-debugger for
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Persistent memory and knowledge graphs for AI agents. Hybrid search, context checkpoints, and more.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vbj1808/retrieval-lens'
If you have feedback or need assistance with the MCP directory API, please join our Discord server