MCP Server: Demo

Created By
jubalma year ago
Demo MCP Server build using Cloudflare MCPAgent Durable Objects and D1 database
Overview

What is MCP Server?

MCP Server is a demonstration project that showcases how to build an MCP (Model Context Protocol) server using Cloudflare's MCPAgent Durable Objects and a D1 database.

How to use MCP Server?

To use the MCP Server, clone the repository, install the dependencies, and run the development server. You can also deploy it to Cloudflare Workers for production use.

Key features of MCP Server?

  • Integration with a D1 database for data retrieval.
  • Schema management with SQL migration files.
  • Durable Object implementation for stateful interactions.
  • Query tool for executing SQL queries.
  • Introspection tool for understanding database structure.
  • Integration tests for validating functionality.

Use cases of MCP Server?

  1. Building scalable applications that require database interactions.
  2. Implementing real-time data processing with server-sent events.
  3. Developing tools that leverage the Model Context Protocol for enhanced data management.

FAQ from MCP Server?

  • What technologies does MCP Server use?

MCP Server uses Cloudflare Workers, Durable Objects, and a D1 database.

  • Is there a license for MCP Server?

Yes, MCP Server is licensed under the MIT License.

  • How can I deploy MCP Server?

You can deploy MCP Server to Cloudflare Workers using the provided deployment scripts.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jubalm
Star
0
Language
TypeScript
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