Building a Remote MCP Server on Cloudflare (Without Auth)

Created By
hekmon8a year ago
Overview

What is MCP Server on Cloudflare?

MCP Server on Cloudflare is a project that allows users to deploy a remote Model Context Protocol (MCP) server without requiring authentication, utilizing Cloudflare Workers.

How to use MCP Server on Cloudflare?

To use the MCP Server, you can deploy it directly to Cloudflare Workers using the provided deployment button or via command line. After deployment, you can connect to it from the Cloudflare AI Playground or local MCP clients.

Key features of MCP Server on Cloudflare?

  • Easy deployment to Cloudflare Workers without authentication.
  • Customizable tools that can be defined in the server's initialization method.
  • Compatibility with Cloudflare AI Playground for remote interactions.

Use cases of MCP Server on Cloudflare?

  1. Deploying a remote server for AI tools without authentication.
  2. Connecting various clients to the MCP server for enhanced functionality.
  3. Customizing the server with specific tools for different applications.

FAQ from MCP Server on Cloudflare?

  • Can I customize the tools on my MCP server?

Yes! You can define your own tools in the init() method of the server.

  • Is authentication required for using the MCP server?

No, this server is designed to operate without authentication.

  • How do I connect my local client to the MCP server?

You can use the mcp-remote proxy to connect your local clients to the deployed MCP server.

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

Recommend Servers

View All
Crevio

a day 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)

19 hours ago