Building a Remote MCP Server on Cloudflare (Without Auth)

Created By
BiteBase-Intelligencea year ago
Overview

What is the MCP Server?

The MCP Server is a remote server that can be deployed on Cloudflare Workers without requiring authentication, allowing for easy access and integration with various tools.

How to use the MCP Server?

To use the MCP Server, you can deploy it directly to Cloudflare Workers using the provided deployment button or command line instructions. You can also connect to it from the Cloudflare AI Playground or local MCP clients like Claude Desktop.

Key features of the MCP Server?

  • Deployable on Cloudflare Workers without authentication.
  • Customizable with user-defined tools.
  • Connectable from Cloudflare AI Playground and local MCP clients.

Use cases of the MCP Server?

  1. Hosting a remote server for AI tools.
  2. Integrating with Cloudflare AI Playground for enhanced functionality.
  3. Connecting local applications to a remote server for processing.

FAQ from the MCP Server?

  • Can I customize the tools on my MCP Server?

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

  • Is authentication required for the MCP Server?

No, this server is designed to operate without authentication for ease of access.

  • 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
BiteBase-Intelligence
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

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

a day ago