Workers Mcp

Created By
geelena year ago
Talk to a Cloudflare Worker from Claude Desktop!
Overview

What is Workers Mcp?

Workers Mcp is a tool designed to facilitate communication between Claude Desktop and Cloudflare Workers, enabling developers to customize their worker functionality to match user needs.

How to use Workers Mcp?

To use Workers Mcp, follow these steps: 1) Generate a new Cloudflare Worker using npx create-cloudflare@latest. 2) Install Workers Mcp with npm install workers-mcp and refer to the generated help instructions with npx workers-mcp help. 3) Implement your Worker logic and deploy it using the provided commands.

Key features of Workers Mcp?

  • CLI tooling and logic for seamless integration between Claude Desktop and Cloudflare Workers
  • Simple methods to create and deploy workers
  • Support for generating secrets and handling authentication

Use cases of Workers Mcp?

  1. Building interactive applications using Cloudflare Workers that respond dynamically to user input in Claude Desktop.
  2. Developing customized logic for data processing directly from the desktop interface.
  3. Creating educational or entertaining functionalities powered by serverless architecture.

FAQ from Workers Mcp?

  • Can I use Workers Mcp with existing Cloudflare Workers?

Yes! You can integrate it with existing workers by routing your fetch calls accordingly.

  • Are there any prerequisites to using Workers Mcp?

Basic knowledge of Node.js and Cloudflare Workers is recommended to effectively implement this tool.

  • Is there support for asynchronous operations?

Yes! The worker methods can handle asynchronous operations using JavaScript Promises.

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