Remote MCP Server on Cloudflare

Created By
kartik71a year ago
Overview

what is Remote MCP Server on Cloudflare?

Remote MCP Server on Cloudflare is a server that allows users to run a Model Context Protocol (MCP) server on Cloudflare Workers, enabling remote access and interaction with various tools through a web interface.

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 on Cloudflare Workers with OAuth login.
  • Local development and testing capabilities.
  • Integration with MCP Inspector for exploring APIs.
  • Ability to connect with Claude Desktop for advanced tool usage.

use cases of Remote MCP Server on Cloudflare?

  1. Running a remote MCP server for various applications.
  2. Connecting different clients to the MCP server for tool access.
  3. Debugging and testing MCP interactions locally before deployment.

FAQ from Remote MCP Server on Cloudflare?

  • Can I run this server without Cloudflare?

No, this server is designed to run on Cloudflare Workers.

  • Is there a way to test the server locally?

Yes, you can run the server locally using the provided commands and connect via the MCP Inspector.

  • What if I encounter issues while connecting?

You can debug by restarting the server or clearing the authentication files as suggested in the documentation.

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