Cloudflare Mcp Server
ListedHelps with Cloudflare, MCP tools, server as part of deploying and managing cloud infrastructure workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add ovachiever/droid-tings --skill cloudflare-mcp-server -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
ovachiever
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: provider.com, worker.dev.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
worker.devundeclaredprovider.comundeclaredWhat it found (3 of 12)
- skills/cloudflare-mcp-server/references/debugging-guide.md:14contacts worker.dev
curl https://worker.dev/ - skills/cloudflare-mcp-server/references/debugging-guide.md:23contacts worker.dev
curl https://worker.dev/sse - skills/cloudflare-mcp-server/references/debugging-guide.md:286contacts worker.dev
curl https://worker.dev/sse # Main endpoint
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned ovachiever/droid-tings at 7acd12a754.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 7acd12a754
- Scanned
- 20 files, 7,338 lines
About this skill
The Cloudflare MCP Server enables AI agents to interact directly with the Cloudflare platform, allowing for automated management of DNS records, SSL/TLS certificates, and worker deployments. It bridges the gap between natural language commands and Cloudflare's API capabilities.
When to use it
- Automating routine infrastructure tasks like updating DNS entries or rotating SSL certificates without manual login.
- Deploying and managing Cloudflare Workers dynamically based on real-time data analysis.
- Integrating Cloudflare security features, such as WAF rule adjustments, into automated monitoring workflows.
- Streamlining multi-account management by executing bulk operations across different Cloudflare zones.
Key capabilities
- Direct API integration with the Cloudflare platform for real-time resource manipulation.
- Support for managing DNS records, SSL/TLS settings, and Worker scripts.
- Facilitates secure authentication mechanisms to handle sensitive infrastructure changes.
- Enables complex orchestration of cloud resources through natural language prompts.
Example prompts
- "Update the A record for example.com to point to 192.0.2.1."
- "Deploy a new Cloudflare Worker script that caches static assets for 24 hours."
- "Rotate the SSL certificate for my production domain and verify the status."
Tips & gotchas
Ensure your AI agent has appropriate API tokens with the necessary scopes (e.g., Zone:Edit, Worker:Edit) before attempting operations. Complex configurations may require breaking down tasks into smaller, sequential steps to avoid rate limiting or permission errors.