Remote MCP Server on Cloudflare

Created By
drillana year ago
Overview

What is Remote MCP Server on Cloudflare?

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

How to use the Remote MCP Server?

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

Key features of the Remote MCP Server?

  • Easy setup of a remote MCP server on Cloudflare Workers.
  • OAuth login for secure access.
  • Integration with tools like MCP Inspector and Claude Desktop.

Use cases of the Remote MCP Server?

  1. Developing and testing MCP APIs locally.
  2. Connecting remote clients to the MCP server for tool invocation.
  3. Facilitating secure access to the MCP server through OAuth.

FAQ from Remote MCP Server?

  • Can I run the MCP server locally?

Yes! You can run the MCP server locally by following the setup instructions provided in the documentation.

  • How do I connect to the MCP server?

You can connect to the MCP server using the MCP Inspector or by configuring your client application to point to the server's URL.

  • Is there support for debugging?

Yes, the project includes debugging tips for troubleshooting connection issues.

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

3 hours ago