bwt
// mcp server

Cloudflare MCP Gateway

experimental Cloudflare Worker Auth: Signed request

Community Cloudflare Worker that mediates authenticated MCP traffic to WordPress sites behind a CDN.

// capabilities
// editorial

An open-source community Cloudflare Worker that sits between an MCP client (Claude Desktop, Cursor, custom agent) and a WordPress install. Handles authentication, request signing, rate limiting, and audit logging at the edge so the WordPress side stays simple. Particularly useful when a managed-WP environment cannot run additional plugins but can route through Cloudflare.

Pros

  • No WordPress-side install needed; works with any WP behind Cloudflare
  • Edge-level rate limiting and authentication
  • Audit log of every agent action stored in Workers KV
  • Composable with the other MCP servers as a frontend layer

Cons

  • Cloudflare-specific; not portable to other CDN providers
  • Experimental status, expect rapid breaking changes
  • Limited capability surface on its own (mediates, does not act)
// methodology

Status semantics

GA: published, documented, intended for production use. Beta: feature-complete but rough edges. Alpha: usable for evaluation, expect breaking changes. Experimental: research-only, not safe for production.

Capability tags

Capability tags reflect what an agent can do via the MCP server, not what the underlying WordPress install supports. A "post-management" capability means the MCP server exposes posts as MCP tools; whether the agent has permission to use them depends on the authentication model.