Building a Remote MCP Server on Cloudflare (Without Auth)

Created By
SanthoshSettya 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 using the command line to create it locally.

Key features of Remote MCP Server Authless?

  • Deploys a remote MCP server without authentication on Cloudflare.
  • 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 tools.
  2. Connecting various AI clients to a centralized MCP server.
  3. Facilitating easy access to AI tools from the Cloudflare AI Playground.

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 configuration.

  • 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 to connect your local clients to the remote MCP server.

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

Recommend Servers

View All
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.

8 hours ago