This MCP server provides an interface for agents like Cursor to interact with the Cloudflare REST API through the Model Control Protocol. It allows you to manage Cloudflare resources programmatically using an agent as your assistant.
Follow these steps to set up the Cloudflare API MCP server:
bun create mcp --clone https://github.com/zueai/cloudflare-api-mcp
Open Cursor and navigate to Cursor Settings -> MCP -> Add new MCP server
, then paste the command that was copied to your clipboard.
Upload your Cloudflare API credentials as worker secrets:
bunx wrangler secret put CLOUDFLARE_API_KEY
bunx wrangler secret put CLOUDFLARE_API_EMAIL
The MCP server provides various tools to interact with Cloudflare's API. Each method in the MyWorker
class represents an available tool that your agent can use.
You can create DNS records using the MCP server. For example:
createDNSRecord(zoneId, name, content, type, comment, proxied)
Where:
zoneId
: The ID of the zone to create the record inname
: The name of the DNS recordcontent
: The content of the DNS recordtype
: The type of DNS record (CNAME, A, TXT, or MX)comment
: Optional comment for the DNS recordproxied
: Optional boolean indicating whether to proxy the record through CloudflareIf you need to develop locally, add your Cloudflare credentials to the .dev.vars
file:
CLOUDFLARE_API_KEY=<your-cloudflare-api-key>
CLOUDFLARE_API_EMAIL=<your-cloudflare-api-email>
To deploy changes to your MCP server:
bun run deploy
You can extend the functionality by adding new methods to the MyWorker
class in src/index.ts
. Each function automatically becomes an MCP tool available to your agent.
When creating new tools, use proper JSDoc comments:
/**
* 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.
*/
The JSDoc format is important as:
@param
tags define parameters with types and descriptions@return
tag specifies what the tool returnsTo add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "cloudflare-api-mcp" '{"command":"bunx","args":["cloudflare-api-mcp"]}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cloudflare-api-mcp": {
"command": "bunx",
"args": [
"cloudflare-api-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"cloudflare-api-mcp": {
"command": "bunx",
"args": [
"cloudflare-api-mcp"
]
}
}
}
3. Restart Claude Desktop for the changes to take effect