Building a Remote MCP Server on Cloudflare (Without Auth)

Created By
cdtaita year ago
Overview

What is Remote MCP Server Authless?

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

How to use Remote MCP Server Authless?

To use this project, you can deploy the MCP server directly to Cloudflare Workers using the provided deployment button or by running a command in your terminal. You can also connect to the server from the Cloudflare AI Playground or local MCP clients.

Key features of Remote MCP Server Authless?

  • 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 Remote MCP Server Authless?

  1. Deploying a secure and customizable remote server for AI applications.
  2. Connecting various tools and services to a centralized MCP server.
  3. Facilitating easy access to AI tools from different platforms.

FAQ from Remote MCP Server Authless?

  • 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 authentication required for this MCP server?

No, this project is designed to work without authentication.

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

You can use the mcp-remote proxy and follow the configuration steps provided in the documentation.

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