Pin Wen

Created By
OpenAgentPlatforma year ago
Overview

what is Dive?

Dive is an open-source MCP Host Desktop Application that integrates seamlessly with various LLMs (Large Language Models) that support function calling capabilities.

how to use Dive?

To use Dive, download the appropriate version for your operating system (Windows, MacOS, or Linux) and follow the installation instructions. Configure your MCP settings to connect with LLMs and utilize the available tools.

key features of Dive?

  • Universal LLM Support for models like ChatGPT, Anthropic, and OpenAI-compatible models.
  • Cross-Platform compatibility for Windows, MacOS, and Linux.
  • Multi-Language Support including Traditional and Simplified Chinese, English, Spanish, Japanese, and Korean.
  • Advanced API Management with support for multiple API keys and model switching.
  • Custom Instructions for personalized AI behavior.
  • Auto-Update Mechanism for keeping the application up to date.

use cases of Dive?

  1. Integrating various AI models for enhanced functionality.
  2. Developing custom AI applications using LLMs.
  3. Utilizing tools like Fetch and Youtube-dl for data retrieval and media downloading.

FAQ from Dive?

  • Is Dive free to use?

Yes! Dive is open-source and free for everyone.

  • What platforms does Dive support?

Dive is available for Windows, MacOS, and Linux.

  • How can I contribute to Dive?

You can contribute by reporting issues, suggesting features, or submitting pull requests on GitHub.

Server Config

{
  "mcpServers": {
    "echo": {
      "transport": "stdio",
      "enabled": false,
      "command": "node",
      "args": [
        "/Users/biggo2/.dive/scripts/echo.js"
      ],
      "env": {},
      "url": null,
      "headers": null,
      "extraData": null
    }
  }
}
Project Info
Created At
a year ago
Updated At
10 months ago
Author Name
OpenAgentPlatform
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