Image

Created By
cwinuxa year ago
Overview

what is DeerFlow?

DeerFlow is a community-driven Deep Research framework that integrates language models with specialized tools for tasks like web search, crawling, and Python code execution, aimed at enhancing research efficiency.

how to use DeerFlow?

To use DeerFlow, clone the repository from GitHub, install the required dependencies, configure your environment, and run the project either through a console UI or a web UI.

key features of DeerFlow?

  • Integration with multiple search engines for comprehensive data retrieval.
  • Human-in-the-loop capabilities for interactive research planning.
  • Automated report generation and content creation, including podcasts and presentations.
  • Modular architecture for flexible research workflows.

use cases of DeerFlow?

  1. Conducting in-depth research on various topics.
  2. Generating comprehensive reports and presentations.
  3. Creating podcasts based on research findings.
  4. Collaborating with AI to refine research plans.

FAQ from DeerFlow?

  • Is DeerFlow open source?

Yes! DeerFlow is open source and available under the MIT License.

  • What programming languages does DeerFlow support?

DeerFlow is developed in Python and includes a web UI written in Node.js.

  • Can I customize the research process?

Yes! DeerFlow allows for customization of research plans and supports various configurations.

Server Config

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-github"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cwinux
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago