DxSure MCP Server and Client Setup

Created By
mondweepa year ago
This is a foundational code base to understand how to create remote mcp servers in cloudflare using the SPARC framework
Overview

what is DxSure MCP Server and Client Setup?

DxSure MCP Server and Client Setup is a foundational code base designed to help users create remote Model Context Protocol (MCP) servers using the SPARC framework on Cloudflare.

how to use DxSure MCP Server and Client Setup?

To use this project, configure the MCP client to connect to your remote MCP server on Cloudflare, deploy the client, and set the MCP server URL in your application settings.

key features of DxSure MCP Server and Client Setup?

  • Core MCP server hosted on Cloudflare Workers.
  • Proxy client for connecting to the MCP server.
  • GitHub OAuth authentication option.
  • Tools for adding numbers and currency conversion.

use cases of DxSure MCP Server and Client Setup?

  1. Hosting tools that require remote access via MCP.
  2. Integrating with Cursor for enhanced functionality.
  3. Developing and deploying custom tools on Cloudflare.

FAQ from DxSure MCP Server and Client Setup?

  • How do I troubleshoot connection issues?

Check the server URL configuration and ensure your Cloudflare worker is running properly.

  • Can I add more tools to the MCP server?

Yes! You can modify the source code to add more tools and redeploy the server.

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