Remote MCP Server on Cloudflare

Created By
threepointonea year ago
Overview

what is Remote MCP Server on Cloudflare?

Remote MCP Server on Cloudflare is a tool that allows users to set up a remote Model Context Protocol (MCP) server using Cloudflare Workers, complete with OAuth login functionality.

how to use Remote MCP Server on Cloudflare?

To use the Remote MCP Server, clone the repository, install dependencies, and run the server locally. You can then connect to the server using the MCP Inspector or integrate it with Claude Desktop for enhanced functionality.

key features of Remote MCP Server on Cloudflare?

  • Easy setup of a remote MCP server on Cloudflare Workers.
  • OAuth login integration.
  • Local development and testing capabilities.
  • Compatibility with MCP Inspector and Claude Desktop.

use cases of Remote MCP Server on Cloudflare?

  1. Setting up a remote server for model context protocol applications.
  2. Connecting various clients like Claude Desktop to the MCP server.
  3. Debugging and testing MCP functionalities locally before deployment.

FAQ from Remote MCP Server on Cloudflare?

  • Can I run the MCP server locally?

Yes! You can develop and test the MCP server locally before deploying it to Cloudflare.

  • How do I connect Claude Desktop to my MCP server?

You need to update the Claude configuration file with your MCP server's URL and restart Claude.

  • What should I do if I encounter issues?

Restarting Claude or connecting directly via command line can help resolve issues.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
threepointone
Star
2
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.

21 hours ago