Cloudflare MCP

What is Cloudflare MCP?

Cloudflare MCP is a template repository for creating and deploying a Model Context Protocol (MCP) server on Cloudflare Workers. It is intended for developers who want to build custom MCP servers that run on Cloudflare’s edge network and can be integrated with AI agents.

How to use Cloudflare MCP?

To get started, run npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless to create a new project from the template. Navigate into the project directory and run npm start to run the server locally. For production, deploy with npm run deploy, which publishes the server as a Cloudflare Worker with an SSE endpoint.

Key features of Cloudflare MCP

• Creates a new MCP server using a Cloudflare-provided template
• Runs locally with a single npm start command
• Deploys to Cloudflare Workers with npm run deploy
• Supports testing via MCP Inspector and Cloudflare Playground
• Uses SSE transport for remote MCP communication
• Requires only Node.js, Wrangler CLI, and a Cloudflare account

Use cases of Cloudflare MCP

• Build custom MCP servers to expose tools and resources to AI agents
• Deploy MCP servers at the edge for low-latency access
• Rapidly prototype and test MCP tools using Cloudflare’s developer tools
• Integrate Cloudflare Workers’ capabilities (e.g., KV, D1, AI) into MCP toolkits

FAQ from Cloudflare MCP

What are the prerequisites for using Cloudflare MCP?

You need Node.js (version 18 or later), the Wrangler CLI (npm install -g wrangler), and a Cloudflare account for deployments.

How do I test my MCP server locally?

Run npm start to start the server, then use npx @modelcontextprotocol/inspector to inspect and test your tools and resources. You can also connect to the server using the Cloudflare Playground at https://playground.ai.cloudflare.com/.

Where is the MCP server deployed?

It deploys to Cloudflare Workers at a URL like https://my-mcp-server.<your-account>.workers.dev/sse, using Server-Sent Events (SSE) as the transport protocol.

Does the template include authentication?

The template is labeled “authless”, meaning no built-in authentication is included. Users may need to add their own authentication layer for production use.