Remote MCP Server on Cloudflare

Created By
chjtxwda 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, enabling OAuth login and interaction with various tools.

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 functionality.
  • Integration with MCP Inspector for exploring APIs.
  • Compatibility with Claude Desktop for advanced tool usage.

use cases of Remote MCP Server on Cloudflare?

  1. Setting up a remote server for API exploration.
  2. Connecting various tools to a centralized MCP server.
  3. Facilitating OAuth-based authentication for secure access.

FAQ from Remote MCP Server on Cloudflare?

  • Can I run the MCP server locally?

Yes! You can run the MCP server locally and connect to it using the MCP Inspector.

  • How do I deploy the server to Cloudflare?

You can deploy the server by creating a KV namespace and following the deployment instructions in the documentation.

  • What should I do if I encounter issues?

Restarting the server or clearing the authentication files may help resolve issues.

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

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour 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