Skip to main content
Glama
lihongwen

Deep Research MCP Server

by lihongwen

MCP Server for Deep Research

MCP Server for Deep Research is a powerful tool designed for conducting comprehensive research on complex topics. It helps you explore questions in depth, find relevant sources, and generate structured research reports with proper citations.

šŸ”¬ Your personal AI Research Assistant - turning complex research questions into comprehensive, well-cited reports.

✨ What's New

Latest Major Update: Advanced Research Methodology (v0.2.0)

This version introduces a publication-quality research framework with significant depth enhancements:

šŸŽÆ Intelligent Complexity Assessment

  • Automatically evaluates question complexity (Simple/Moderate/Complex/Highly Complex)

  • Dynamically adjusts research depth and methodology based on complexity

  • Scales from quick comparisons to comprehensive multi-disciplinary analyses

šŸ“Š Multi-Layer Progressive Research

  • Layer 1 (Overview): Foundational understanding for all questions

  • Layer 2 (Deep Dive): Focused investigation for moderate+ complexity

  • Layer 3 (Expert Analysis): Cutting-edge insights for complex topics

🌳 Dynamic Hierarchical Subquestions

  • Adaptive quantity: 3-4 questions (simple) → 7-8+ questions (highly complex)

  • Tree structure: Core questions with secondary deep-dive sub-questions

  • Priority tagging: High/Medium/Low with dependency mapping

šŸ” Critical Analysis Framework

  • Source Credibility Assessment: Authority, recency, bias evaluation

  • Evidence Quality Grading: Strong/Moderate/Weak/Speculative classifications

  • Viewpoint Comparison: Mainstream vs. alternative perspectives

  • Logical Coherence Checking: Causation vs. correlation, assumption identification

  • Hypothesis Testing: Formulate and evaluate testable hypotheses

šŸ› ļø Professional Analysis Frameworks

Choose from 9+ structured methodologies:

  • SWOT Analysis (strategic evaluation)

  • PEST/PESTEL Analysis (macro-environmental factors)

  • 5W2H Framework (diagnostic deep-dive)

  • Comparative Analysis (multi-dimensional comparison)

  • Trend Analysis (historical → present → future)

  • Case Study Method (learn from examples)

  • Stakeholder Analysis (perspective mapping)

  • Evidence Pyramid (scientific rigor)

  • Systems Thinking (interconnections and feedback loops)

🌐 Interdisciplinary Synthesis

  • Tags questions with relevant disciplines: Technical, Economic, Social, Ethical, Legal, Scientific, Historical

  • Identifies cross-perspective patterns and tensions

  • Generates emergent insights from integrated analysis

šŸ“„ Publication-Quality Reports

Enhanced structure with:

  • Executive Summary (200-300 words)

  • Methodology Section (framework justification)

  • Critical Analysis (separate from findings)

  • Synthesis & Discussion (interdisciplinary integration)

  • Confidence Levels (HIGH/MODERATE/LOW/SPECULATIVE)

  • Research Limitations (transparent acknowledgment)

  • Recommendations (stakeholder-specific actions)

  • Further Research Directions

  • Glossary (technical terms)

  • Supplementary Data (tables, charts)

āœ… Enhanced Quality Standards

  • Evidence mapping with strength ratings

  • Bias and limitation assessment

  • Confidence level assignment for all conclusions

  • Proper academic-style citations

  • Acknowledgment of uncertainty and knowledge boundaries


Core Features (All Versions)

  • šŸ› ļø Direct Tool Access: Call the start_deep_research tool directly from Claude Desktop

  • šŸ“Š Structured Research Workflow: Guided process from question elaboration to final report

  • 🌐 Web Search Integration: Leverages Claude's built-in search capabilities

  • šŸ“ Professional Reports: Generates well-formatted research reports as artifacts

Related MCP server: MCP Server for Deep Research

šŸš€ Quick Start

Prerequisites

Installation

  1. Clone this repository

    git clone https://github.com/lihongwen/deepresearch-mcpserver.git
    cd deepresearch-mcpserver
  2. Install dependencies

    uv sync
  3. Configure Claude Desktop

    Edit your Claude Desktop config file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

    Add the following configuration:

    {
      "mcpServers": {
        "mcp-server-deep-research": {
          "command": "uv",
          "args": [
            "--directory",
            "/path/to/your/deepresearch-mcpserver",
            "run",
            "mcp-server-deep-research"
          ]
        }
      }
    }
  4. Restart Claude Desktop

  5. Start Researching

    • Use the prompt template: "Start deep research on [your question]"

    • Or call the start_deep_research tool directly

    • Watch as Claude conducts comprehensive research and generates a detailed report

šŸŽÆ Complete Research Workflow

The Deep Research MCP Server offers a sophisticated 5-phase research methodology:

Phase 1: Preliminary Analysis & Research Design

  • Conceptual Clarification: Defines key terms with precision

  • Domain Mapping: Identifies primary knowledge domains and intersections

  • Stakeholder Identification: Maps who cares about this question and why

  • Complexity Assessment: Evaluates as Simple/Moderate/Complex/Highly Complex

  • Strategy Selection: Chooses appropriate analytical frameworks and research depth

Phase 2: Hierarchical Question Decomposition

  • Dynamic Subquestion Generation: Creates 3-8 questions based on complexity

  • Tree Structure: Core questions with secondary deep-dive sub-questions

  • Quality Criteria: Specific, focused, collectively exhaustive, mutually exclusive

  • Priority & Dependencies: Tags questions with importance and relationships

  • Interdisciplinary Tagging: Labels questions with relevant disciplinary perspectives

Phase 3: Layered Information Gathering

  • Layer 1 (Overview): Broad searches, credibility assessment, evidence classification

  • Layer 2 (Deep Dive): Focused searches, comparative analysis, pattern identification

  • Layer 3 (Expert Analysis): Frontier research, expert discourse, future trajectories

  • Source Credibility Ratings: High/Medium/Low based on authority, recency, bias

  • Evidence Classification: Strong/Moderate/Weak/Speculative based on rigor

Phase 4: Critical Analysis & Synthesis

  • Evidence Mapping: Central claims, supporting/contradicting evidence, gaps

  • Logical Coherence Check: Causation vs. correlation, reasoning validity

  • Bias Assessment: Selection, confirmation, temporal, publication bias

  • Hypothesis Testing: Formulate, evaluate, conclude (Supported/Partial/Not Supported)

  • Confidence Levels: Assign HIGH/MODERATE/LOW/SPECULATIVE to conclusions

  • Interdisciplinary Synthesis: Cross-perspective patterns, emergent insights, systems understanding

Phase 5: Comprehensive Report Generation

  • Executive Summary: 200-300 word standalone overview

  • Table of Contents: Auto-generated navigation

  • Introduction: Context, importance, scope, key concepts

  • Methodology: Complexity rationale, framework selection, limitations

  • Findings: Detailed subsections per subquestion with evidence ratings

  • Critical Analysis: Evidence strength, contradictions, bias evaluation

  • Synthesis & Discussion: Integrated insights, patterns, contextual factors

  • Conclusions: Direct answers with confidence levels and implications

  • Recommendations: Stakeholder-specific actionable guidance

  • Research Limitations: Transparent acknowledgment of constraints

  • Further Research: Identified knowledge gaps and future directions

  • References: Comprehensive citations with proper formatting

  • Appendices: Glossary of terms, supplementary data

šŸ’” Usage Examples

Simple Question

User: "Start deep research on: What is the difference between REST and GraphQL APIs?"

Claude will:
1. Assess as SIMPLE complexity → Layer 1 research only
2. Generate 3-4 focused subquestions (characteristics, use cases, trade-offs)
3. Select Comparative Analysis framework
4. Perform targeted searches with credibility assessment
5. Generate concise report with comparison table

Moderate Question

User: "Start deep research on: What are the applications and challenges of blockchain in supply chain management?"

Claude will:
1. Assess as MODERATE complexity → Layer 1 + Layer 2 research
2. Generate 5-6 core + 2-3 deep-dive subquestions
3. Select SWOT Analysis + Case Study Method + Trend Analysis
4. Perform overview AND focused deep-dive searches
5. Include critical analysis of evidence quality
6. Generate comprehensive report with multiple case studies and confidence levels

Complex Question

User: "Start deep research on: How does climate change impact global food security, and what are effective adaptation strategies?"

Claude will:
1. Assess as COMPLEX → Layer 1 + Layer 2 + Layer 3 research
2. Generate 6-7 core + 3-5 deep-dive subquestions with dependencies
3. Select Systems Thinking + PEST + Stakeholder Analysis + Comparative Analysis
4. Tag with multiple disciplines: Scientific, Economic, Social, Political, Ethical
5. Perform overview + focused + expert-level research
6. Include hypothesis testing (e.g., "Climate-resilient crops maintain yields under 2°C warming")
7. Generate publication-quality report with executive summary, methodology justification, 
   critical analysis, interdisciplinary synthesis, stakeholder recommendations, 
   research limitations, and glossary

šŸ”§ How It Works

  1. Call the Tool: Invoke start_deep_research with your research question

  2. Follow the Workflow: Claude follows a structured research process

  3. Review the Report: Get a comprehensive report as an artifact

  4. Cite Sources: All information is properly cited with source URLs

šŸ“¦ Components

Tools

  • start_deep_research: Initiates a comprehensive research workflow on any topic

    • Input: research_question (string)

    • Output: Structured research guidance and workflow

Prompts

  • deep-research: Pre-configured prompt template for starting research tasks

Resources

  • Dynamic research state tracking

  • Progress notes and findings storage

āš™ļø Configuration

Claude Desktop Config Locations

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Development Setup (Local)

{
  "mcpServers": {
    "mcp-server-deep-research": {
      "command": "uv",
      "args": [
        "--directory",
        "C:\\Users\\YourUsername\\path\\to\\deepresearch-mcpserver",
        "run",
        "mcp-server-deep-research"
      ]
    }
  }
}

Production Setup (Published)

If published to PyPI:

{
  "mcpServers": {
    "mcp-server-deep-research": {
      "command": "uvx",
      "args": [
        "mcp-server-deep-research"
      ]
    }
  }
}

šŸ› ļø Development

Setup Development Environment

# Clone the repository
git clone https://github.com/lihongwen/deepresearch-mcpserver.git
cd deepresearch-mcpserver

# Install dependencies
uv sync

# Run in development mode
uv run mcp-server-deep-research

Testing

# Install the MCP Inspector for testing
npx @modelcontextprotocol/inspector uv --directory . run mcp-server-deep-research

Building and Publishing

  1. Sync Dependencies

    uv sync
  2. Build Distributions

    uv build

    Generates source and wheel distributions in the dist/ directory.

  3. Publish to PyPI (if you have publishing rights)

    uv publish

Project Structure

deepresearch-mcpserver/
ā”œā”€ā”€ src/
│   └── mcp_server_deep_research/
│       ā”œā”€ā”€ __init__.py
│       └── server.py           # Main MCP server implementation
ā”œā”€ā”€ pyproject.toml              # Project configuration
ā”œā”€ā”€ README.md                   # This file
└── LICENSE                     # MIT License

šŸ¤ Contributing

Contributions are welcome! Here's how you can help:

  1. šŸ› Report Bugs: Open an issue describing the bug

  2. šŸ’” Suggest Features: Share your ideas for improvements

  3. šŸ”§ Submit Pull Requests: Fix bugs or add features

  4. šŸ“– Improve Documentation: Help make the docs better

Contribution Guidelines

  • Follow the existing code style

  • Add tests for new features

  • Update documentation as needed

  • Write clear commit messages

šŸ“ Changelog

Version 0.2.0 (Latest) - Major Research Methodology Overhaul

  • āœ… Intelligent Complexity Assessment: Automatic evaluation and adaptive methodology

  • āœ… Multi-Layer Progressive Research: 3-tier depth system (Overview/Deep-Dive/Expert)

  • āœ… Dynamic Hierarchical Subquestions: 3-8 questions based on complexity with tree structure

  • āœ… Critical Analysis Framework: Source credibility, evidence grading, bias assessment, hypothesis testing

  • āœ… 9+ Analytical Frameworks: SWOT, PEST, 5W2H, Comparative, Trend, Case Study, Stakeholder, Evidence Pyramid, Systems Thinking

  • āœ… Interdisciplinary Synthesis: Multi-perspective analysis with cross-domain insights

  • āœ… Publication-Quality Reports: Executive summary, methodology, critical analysis, limitations, recommendations, glossary

  • āœ… Confidence Level System: HIGH/MODERATE/LOW/SPECULATIVE ratings for all conclusions

  • āœ… Enhanced Evidence Standards: Credibility ratings, evidence classification, citation requirements

  • āœ… Comprehensive Testing Guide: Test cases for Simple/Moderate/Complex/Highly Complex questions

Version 0.1.0 - Initial Release

  • āœ… Added start_deep_research tool for direct invocation

  • āœ… Enhanced research workflow with structured prompts

  • āœ… Improved error handling and logging

  • āœ… Updated documentation with examples

šŸ™ Acknowledgments

This project is based on the original mcp-server-deep-research by reading-plus-ai.

Special thanks to:

  • Anthropic for the MCP protocol and Claude AI

  • The open-source community for inspiration and support

šŸ“œ License

This project is licensed under the MIT License - see the LICENSE file for details.


Made with ā¤ļø for better AI-powered research

Available Tools

1 tool
start_deep_researchB

Conduct comprehensive research on any topic with a systematic, balanced approach. This tool guides thorough research that adapts to question complexity - from simple queries to complex multi-faceted investigations.

KEY FEATURES: • Adaptive depth: Automatically scales research based on question complexity (3-8 subquestions) • Source evaluation: Assesses credibility (High/Medium/Low) and evidence strength (Strong/Moderate/Weak/Speculative) • Multiple perspectives: Examines different viewpoints and competing theories when relevant • Critical analysis: Checks logic, identifies biases, and acknowledges limitations • Clear reporting: Structured reports with executive summary, findings, analysis, and conclusions • Confidence levels: Each conclusion includes confidence rating based on evidence quality • Proper citations: All sources properly attributed with URLs

Works for any research type: historical events, technical topics, current affairs, comparative analyses, scientific questions, cultural topics, and more.

ParametersJSON Schema
NameRequiredDescriptionDefault
research_questionYesThe research question to investigate in depth

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It details key features like adaptive depth, source evaluation, and structured reporting, which adds useful context beyond basic functionality. However, it lacks information on performance aspects such as rate limits, execution time, or error handling, leaving gaps in behavioral understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with bullet points but is overly verbose, listing features that could be condensed. Sentences like 'Works for any research type...' add redundancy. While front-loaded with a clear purpose, it includes excessive detail that doesn't all earn its place, reducing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (deep research with multiple features) and no output schema, the description is moderately complete. It covers the process and features but lacks details on output format, error cases, or practical limitations. Without annotations, it should provide more behavioral context to be fully adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for its single parameter 'research_question,' so the baseline score is 3. The description does not add any additional meaning or examples beyond what the schema provides, such as formatting guidelines or scope constraints for the research question.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'conducts comprehensive research on any topic with a systematic, balanced approach,' specifying the verb 'conduct research' and resource 'any topic.' It distinguishes itself by emphasizing depth and systematic methodology. However, without sibling tools, differentiation is not applicable, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives, as no sibling tools exist. It mentions it 'works for any research type' but lacks context on prerequisites, limitations, or specific scenarios where it's most effective, offering only implied usage without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

B3.2/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'start_deep_research' has a clearly defined and distinct purpose for conducting comprehensive research.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'start_deep_research' follows a clear verb_noun pattern that would be consistent if more tools existed.

Tool Count2/5

A single tool is too few for a server named 'Deep Research MCP Server', which suggests a domain requiring multiple operations. While the tool is comprehensive, the lack of supporting tools (e.g., for follow-up queries, source management, or report customization) makes the surface feel incomplete and thin for the apparent scope.

Completeness2/5

The tool surface is severely incomplete for a deep research domain. There are obvious gaps: no tools for refining research, managing sources, updating findings, or handling different stages of research workflows. The single tool provides a starting point but leaves agents with no way to interact further with the research process.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

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/lihongwen/deepresearch-mcpserver'

If you have feedback or need assistance with the MCP directory API, please join our Discord server