Deep Research

Created By
u14appa year ago
Use any LLMs (Large Language Models) for Deep Research. Support SSE API and MCP server.
Overview

What is Deep Research?

Deep Research is a tool that utilizes various Large Language Models (LLMs) to generate in-depth research reports quickly and efficiently. It supports both Server-Sent Events (SSE) API and Model Context Protocol (MCP) server for enhanced functionality.

How to use Deep Research?

To use Deep Research, you can deploy it on platforms like Vercel or Cloudflare, set up your LLM API key, and start generating research reports by inputting your research topic.

Key features of Deep Research?

  • Rapid generation of comprehensive research reports in about 2 minutes.
  • Multi-platform support for deployment.
  • Privacy-focused, with all data processed locally.
  • Supports multiple LLMs and web search functionalities.
  • Allows for editing and refining research content at any stage.
  • Generates knowledge graphs and maintains research history.

Use cases of Deep Research?

  1. Quickly generating research reports for academic purposes.
  2. Assisting in data analysis for business insights.
  3. Supporting content creation for blogs and articles.

FAQ from Deep Research?

  • Can I use my own LLM?
    Yes, you can set up your own LLM API key to use with Deep Research.

  • Is my data secure?
    Yes, all data is processed locally, ensuring your privacy.

  • What platforms can I deploy it on?
    You can deploy Deep Research on Vercel, Cloudflare, or run it locally.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
u14app
Star
2893
Language
JavaScript
License
MIT 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