Remote MCP Server on Cloudflare

Created By
Mechanicalgoata year ago
Overview

what is Remote MCP Server?

Remote MCP Server is a cloud-based server that allows users to run and connect to a Model Context Protocol (MCP) server on Cloudflare Workers, enabling OAuth login and remote access to defined tools.

how to use Remote MCP Server?

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

key features of Remote MCP Server?

  • Easy setup on Cloudflare Workers
  • OAuth login integration
  • Local development and testing capabilities
  • Connection to remote clients like Claude Desktop

use cases of Remote MCP Server?

  1. Running a remote MCP server for various applications.
  2. Connecting to the server using the MCP Inspector for API exploration.
  3. Integrating with Claude Desktop for advanced tool usage.

FAQ from Remote MCP Server?

  • Can I run the server locally?

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

  • How do I connect to the server?

Use the MCP Inspector or configure Claude Desktop to connect to your MCP server.

  • Is there a way to debug connection issues?

Yes! You can restart Claude or connect directly via command line for troubleshooting.

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

Recommend Servers

View All
Voyei

6 hours 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.

16 hours ago