Remote MCP Server on Cloudflare

Created By
Rahulsree1a year ago
Overview

what is Remote MCP Server on Cloudflare?

The Remote MCP Server on Cloudflare is a server setup that allows users to run a Model Context Protocol (MCP) server on Cloudflare Workers, enabling remote access and interaction with various tools through a web interface.

how to use Remote MCP Server on Cloudflare?

To use the Remote MCP Server, clone the repository, install dependencies, and run the server locally. You can then connect to the MCP Inspector to explore the API and deploy it to Cloudflare for remote access.

key features of Remote MCP Server on Cloudflare?

  • Local development and testing environment for MCP servers.
  • Integration with the MCP Inspector for API exploration.
  • Deployment capabilities to Cloudflare Workers for remote access.
  • Configuration options for connecting various clients like Claude Desktop.

use cases of Remote MCP Server on Cloudflare?

  1. Developing and testing MCP servers locally before deployment.
  2. Connecting remote clients to the MCP server for tool invocation.
  3. Utilizing Cloudflare's infrastructure for scalable server deployment.

FAQ from Remote MCP Server on Cloudflare?

  • Can I run the MCP server without Cloudflare?

Yes, you can run it locally for development purposes.

  • Is there a specific way to connect clients to the MCP server?

Yes, you need to configure the client settings to point to the MCP server's URL.

  • What should I do if I encounter issues?

Restarting the client or checking the connection settings usually helps.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Rahulsree1
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