Are you the author? Sign in to claim
Integrated Model Context Protocol (MCP) to allow the agent to interface with external search APIs and local file systems
A multi-agent research system that decomposes complex queries into targeted sub-questions, searches the web in parallel, scores source credibility, and synthesizes findings into structured markdown reports — accessible via Streamlit UI, MCP tool (Claude Code / Cursor), or Python API.
Give it a broad research question. It returns a structured report with executive summary, key findings, knowledge gaps, and cited sources — in about 10 seconds.
"What are the latest developments in multi-agent AI systems?"
↓
# Research Report: Multi-Agent AI Systems — Latest Developments
## Executive Summary
...
## Key Findings
### How are multi-agent frameworks evolving in 2026?
... [source](https://...) [credibility: high]
## Knowledge Gaps
- No peer-reviewed benchmarks comparing LangGraph vs CrewAI at scale
- ...
## Sources
1. https://arxiv.org/... [high]
2. https://techcrunch.com/... [medium]
Three-node LangGraph pipeline with typed state, parallel search, and 24-hour result caching:
┌──────────┐ ┌────────────────┐ ┌──────────────┐
│ Planner │────▶│ Searcher │────▶│ Synthesizer │
│ (GPT-4o) │ │ (Tavily ×5) │ │ (GPT-4o) │
└──────────┘ └────────────────┘ └──────────────┘
│ │ │
▼ ▼ ▼
3-5 targeted Parallel searches Markdown report
sub-questions with credibility with citations
scoring and knowledge gaps
Planner — Decomposes the query into 3–5 non-overlapping sub-questions using GPT-4o structured output (Pydantic). Context-aware: follow-up queries build on prior research instead of repeating it.
Searcher — Fires all searches concurrently via ThreadPoolExecutor. Each result is tagged with a credibility score (high / medium / unverified) based on domain authority. Graceful per-question error handling.
Synthesizer — Analyzes all evidence, weights high-credibility sources when findings conflict, and produces a structured report at temperature=0.2 for consistency.
Cache — SHA-256 hash of (query + context + search depth). 24-hour TTL. Repeat queries return in <100ms.
git clone https://github.com/sid12super/MCP-Deep-Researcher.git
cd MCP-Deep-Researcher
uv sync
cp .env.example .env
# Add your API keys to .env
streamlit run app.py
Opens at http://localhost:8501 with:
The MCP server exposes the full research pipeline as a tool with Pydantic-validated input, search depth control, and multi-turn conversation support.
Start the server:
uv run server.py
Configure your MCP client — create .mcp.json in your project root:
{
"mcpServers": {
"deep_researcher_mcp": {
"command": "uv",
"args": [
"--directory",
"/absolute/path/to/MCP-Deep-Researcher",
"run",
"server.py"
],
"env": {
"OPENAI_API_KEY": "sk-...",
"TAVILY_API_KEY": "tvly-..."
}
}
}
}
Use it in Claude Code:
Use deep_researcher_research to find the latest developments in multi-agent AI systems
Use deep_researcher_research with search_depth "basic" for a quick comparison of LangGraph vs CrewAI
Use deep_researcher_research to follow up on that — pass the previous report as conversation_context
The tool accepts three parameters:
| Parameter | Type | Default | Description |
|---|---|---|---|
query | string | required | Research question (3–2000 chars) |
search_depth | "basic" | "advanced" | "advanced" | Speed vs. thoroughness tradeoff |
conversation_context | string | "" | Prior research for multi-turn follow-ups |
from agents import run_research
# Simple query
report = run_research("What are the latest AI trends in 2026?")
# With options
report = run_research(
"How does this compare to 2025?",
conversation_context="Previous findings: ...",
search_depth="basic",
)
# Full state (for programmatic access)
result = run_research("Your query", return_full_state=True)
# result["report"], result["query"], result["research_questions"]
Toggle between basic (faster, ~8s) and advanced (comprehensive, ~14s) from the Streamlit sidebar or as an MCP parameter. Each depth caches separately.
Follow-up queries automatically receive prior research context. The planner generates deeper, non-redundant questions instead of repeating covered ground. Reset anytime with "New Research Topic."
Download the full research conversation (all queries and reports) as:
Every source is automatically classified:
The synthesizer weights high-credibility sources more heavily when findings conflict.
Streamlit UI shows live status updates as each pipeline stage completes — questions generated, results retrieved, report synthesized. Cache hits display instantly.
Results are cached by SHA-256 hash of (query + conversation context + search depth) with a 24-hour TTL. Identical requests return in <100ms at zero cost.
├── agents.py # LangGraph pipeline, nodes, caching, credibility scoring
├── server.py # MCP server (FastMCP, Pydantic input, async)
├── app.py # Streamlit UI (chat, exports, progress, sidebar)
├── pyproject.toml # Dependencies (uv)
├── .env.example # API key template
├── .mcp.json # MCP client config (gitignored — contains keys)
├── CLAUDE.md # Claude Code development context
└── test/ # Import, integration, and pipeline tests
| Stage | Time | Notes |
|---|---|---|
| Planner | ~2-3s | GPT-4o structured output |
| Searcher | ~2-3s | Parallel via ThreadPoolExecutor |
| Synthesizer | ~5-8s | GPT-4o at temperature=0.2 |
| Total | ~9-14s | First run |
| Cached | <100ms | Repeat queries within 24h |
Cost per unique query: ~$0.06-0.10 (GPT-4o + Tavily) Cost per cached query: $0.00
| Issue | Fix |
|---|---|
ModuleNotFoundError | Run uv sync |
OpenAI API key not found | Check .env exists with OPENAI_API_KEY |
Tavily API error | Verify key at app.tavily.com |
| Port 8501 in use | streamlit run app.py --server.port 8502 |
| MCP server not found | Ensure .mcp.json is at project root (not inside .claude/) |
| MCP server failed | Test with uv run server.py directly to see errors |
Run Claude Code as an MCP server so any agent can delegate coding tasks to it
Browser automation using accessibility snapshots instead of screenshots
Google's universal MCP server supporting PostgreSQL, MySQL, MongoDB, Redis, and 10+ databases
Official GitHub integration for repos, issues, PRs, and CI/CD workflows