mcp -cloudflare

This MCP server provides a Cloudflare API integration so you can manage your Cloudflare resources through natural language with any MCP client. It exposes a set of tools grouped under KV Store, R2 Storage, D1 Databases, Workers, and Analytics, letting you list, read, create, update, and delete resources like KV namespaces, R2 buckets and objects, D1 databases and queries, Worker scripts, and domain analytics. To get started, install and initialize the server with the given command, then connect your MCP client (Claude Desktop, Cline, Windsurf, or another compatible client) to interact with your Cloudflare account using natural language prompts. The server translates your requests into Cloudflare API calls and returns results in a structured format suitable for subsequent steps in your workflow.

Prerequisites:

• Node.js (LTS) and npm installed on your machine
• Access to a Cloudflare account with API tokens/credentials ready

Install and initialize the MCP Cloudflare server:

# Install and initialize the Cloudflare MCP server (via npx)
npx -y @gutmutcode/mcp-server-cloudflare init

If you prefer cloning and running locally, you can follow a typical Node.js project setup (after forking/cloning the repo):

# Install dependencies
pnpm install || npm install

# Build or prepare if the project requires a build step
pnpm build || npm run build

# Start the server (if a runtime start command is provided by the package)
node dist/index.js run <account-id>

Configure your environment variables to enable Cloudflare access (examples; replace placeholders):

export CLOUDFLARE_ACCOUNT_ID="your-account-id"
export CLOUDFLARE_API_TOKEN="your-api-token"
export CLOUDFLARE_API_TOKEN_PERMISSIONS="read write"

Optionally, refer to the README instructions for connecting Claude Desktop, Cline, Windsurf, or other MCP clients after initialization.

Tips and common issues:

• Ensure your Cloudflare API token has the required scopes for KV, R2, D1, Workers, and analytics access.
• After running the init command, restart your MCP client to detect the new cloudflare tools list.
• Windsurf may limit the number of tools you can use concurrently; plan your tool usage accordingly.
• If you don’t see the cloudflare tools in your MCP client, emit a tools/list command from your client to refresh the available tool set.
• The server supports standard MCP tool commands like worker_list, kv_get, r2_put_object, d1_query, analytics_get, etc. Use these for examples and test queries.
• If you change Cloudflare credentials, restart the MCP server to pick up new tokens.
• For troubleshooting, check network access to Cloudflare APIs and verify that the API token has not expired.