MCP-Deep-Researcher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | OpenAI API key | |
| TAVILY_API_KEY | Yes | Tavily API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deep_researcher_researchA | Run a multi-agent research pipeline that decomposes a query into sub-questions, searches the web in parallel via Tavily, scores source credibility, and synthesizes a comprehensive markdown report with findings, knowledge gaps, and cited sources. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is zero ambiguity among tools. The tool's purpose is clearly defined.
With a single tool, naming consistency is trivially perfect. The name 'deep_researcher_research' is descriptive and follows a clear pattern.
The server is focused on a single, complex task (deep research). One tool is appropriate; adding more would likely complicate the interface unnecessarily.
The single tool covers the entire research pipeline—planning, searching, scoring, synthesizing—with caching. No obvious gaps within its stated purpose.