Building a Remote MCP Server on Cloudflare (Without Auth)

Created By
rosedaela year ago
Overview

What is Remote MCP Server?

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

How to use Remote MCP Server?

To use the Remote MCP Server, you can deploy it directly to Cloudflare Workers using the provided deployment button or command line instructions. You can also customize the server by defining tools in the init() method.

Key features of Remote MCP Server?

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

Use cases of Remote MCP Server?

  1. Deploying a server for AI tools without authentication.
  2. Customizing the server with specific tools for various applications.
  3. Connecting to AI clients like Claude Desktop for enhanced functionality.

FAQ from Remote MCP Server?

  • Can I customize the tools on the MCP server?

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

  • Is authentication required for the Remote MCP Server?

No, this server is designed to operate without authentication.

  • How do I connect to my MCP server from local clients?

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

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

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 hours ago