cloudflare-api MCP Server

Use This MCP server To

Enable Cursor Agent to manage Cloudflare DNS records programmatically Automate Cloudflare firewall rule updates via MCP tools Fetch Cloudflare analytics data for real-time monitoring Deploy and manage Cloudflare Workers through API calls Integrate Cloudflare API access into AI-driven workflows Automate SSL certificate management on Cloudflare Trigger Cloudflare cache purges from natural language commands

README

cloudflare-api-mcp

This is a lightweight Model Control Protocol (MCP) server bootstrapped with create-mcp and deployed on Cloudflare Workers.

This MCP server allows agents (such as Cursor) to interface with the Cloudflare REST API.

It's still under development, I will be adding more tools as I find myself needing them.

Available Tools

See src/index.ts for the current list of tools. Every method in the class is an MCP tool.

Installation

Run the automated install script to clone this MCP server and deploy it to your Cloudflare account:

bun create mcp --clone https://github.com/zueai/cloudflare-api-mcp

Open Cursor Settings -> MCP -> Add new MCP server and paste the command that was copied to your clipboard.
Upload your Cloudflare API key and email to your worker secrets:

bunx wrangler secret put CLOUDFLARE_API_KEY
bunx wrangler secret put CLOUDFLARE_API_EMAIL

Local Development

Add your Cloudflare API key and email to the .dev.vars file:

CLOUDFLARE_API_KEY=<your-cloudflare-api-key>
CLOUDFLARE_API_EMAIL=<your-cloudflare-api-email>

Deploying

Run the deploy script:

bun run deploy

Reload your Cursor window to see the new tools.

How to Create New MCP Tools

To create new MCP tools, add methods to the MyWorker class in src/index.ts. Each function will automatically become an MCP tool that your agent can use.

Example:

/**
 * Create a new DNS record in a zone.
 * @param zoneId {string} The ID of the zone to create the record in.
 * @param name {string} The name of the DNS record.
 * @param content {string} The content of the DNS record.
 * @param type {string} The type of DNS record (CNAME, A, TXT, or MX).
 * @param comment {string} Optional comment for the DNS record.
 * @param proxied {boolean} Optional whether to proxy the record through Cloudflare.
 * @return {object} The created DNS record.
 */
createDNSRecord(zoneId: string, name: string, content: string, type: string, comment?: string, proxied?: boolean) {
    // Implementation
}

The JSDoc comments are important:

First line becomes the tool's description
@param tags define the tool's parameters with types and descriptions
@return tag specifies the return value and type

Learn More

cloudflare-api-mcp FAQ

How do I deploy the cloudflare-api-mcp server?

Use the automated install script with bun create mcp to clone and deploy it to your Cloudflare account.

How do I authenticate the MCP server with Cloudflare?

Upload your Cloudflare API key and email as secrets to your Cloudflare Worker using wrangler secret commands.

Can I add custom tools to this MCP server?

Yes, you can extend the server by adding new methods in the source code as MCP tools.

Is this MCP server compatible with Cursor Agent?

Yes, it is specifically designed to give Cursor Agent access to Cloudflare API functionality.

What Cloudflare API features are currently supported?

The server supports multiple API endpoints; see the src/index.ts file for the current list of available tools.

Is the cloudflare-api-mcp server production-ready?

It is under active development but functional for many Cloudflare API interactions.

How do I update the MCP server after deployment?

Redeploy the updated code using the same deployment process with bun create mcp and wrangler.