Building a Remote MCP Server on Cloudflare (Without Auth)

Created By
LMJayasundaraa year ago
Overview

What is the Remote MCP Server?

The Remote MCP Server is a tool that allows users to deploy a remote Model Context Protocol (MCP) server on Cloudflare Workers without requiring authentication.

How to use the Remote MCP Server?

To use the Remote MCP Server, you can deploy it directly to Cloudflare Workers using the provided deployment button or by using the command line to create it locally. After deployment, connect to the server using the Cloudflare AI Playground or local MCP clients like Claude Desktop.

Key features of the Remote MCP Server?

  • Deploys a remote MCP server without authentication on Cloudflare Workers.
  • Customizable tools can be added to the MCP server.
  • Connects seamlessly with Cloudflare AI Playground and local MCP clients.

Use cases of the Remote MCP Server?

  1. Deploying a server for AI tools without the need for user authentication.
  2. Customizing the server with specific tools for various applications.
  3. Integrating with AI clients for enhanced functionality.

FAQ from the Remote MCP Server?

  • Can I customize the tools on my MCP server?

Yes! You can define and customize tools in the init() method of your server's code.

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

Yes! You can connect local clients like Claude Desktop using the mcp-remote proxy.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
LMJayasundara
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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