MCP Dust Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP Dust Server?

MCP Dust Server is an implementation of a Model Context Protocol (MCP) server designed to interact with Dust agents, facilitating communication and integration with AI models.

how to use MCP Dust Server?

To use the MCP Dust Server, clone the repository from GitHub, install the necessary dependencies, configure environment variables, and start the server and client using npm scripts.

key features of MCP Dust Server?

  • Separate MCP server and test client components
  • Interaction with Dust AI agents via the Dust API
  • Real-time streaming responses using Server-Sent Events (SSE)
  • Full JSON-RPC 2.0 support
  • Robust session management and context preservation
  • Secure API key handling
  • Automatic reconnection for dropped connections

use cases of MCP Dust Server?

  1. Integrating AI agents into applications for enhanced functionality.
  2. Testing and debugging AI interactions through a web interface.
  3. Building custom workflows with multiple AI agents.

FAQ from MCP Dust Server?

  • What is the purpose of the MCP Dust Server?

It serves as a bridge for communication between applications and Dust AI agents.

  • Is the MCP Dust Server open source?

Yes! It is available on GitHub under the MIT license.

  • How can I test the server functionality?

You can use the provided web-based test client to interact with the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
Apache-2.0 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)

6 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago