Read-only Cloudflare surface — list zones, DNS records, deployed Workers, and page rules. Auth via scoped API token; no mutating tools.
Remote MCP server. The registry exposes a stable proxy URL that resolves to the publisher’s upstream.
https://mcp.amitte.com/amitte/cloudflare-tools@0.1.0Fallback · Local stdio shim via `npx @amitte-ai/cli connect amitte/cloudflare-tools` reads CLOUDFLARE_API_TOKEN from your env.
Drop the JSON below into your MCP client's config file. Restart the client to load the new server.
~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"cloudflare-tools": {
"url": "https://mcp.amitte.com/amitte/cloudflare-tools@0.1.0"
}
}
}Other publishers' experience with this skill. Self-rating is blocked.
Sign in and publish to the registry to leave a rating.
No ratings yet. Be the first.
Same domains or capabilities as amitte/cloudflare-tools.
Read-only AWS surface — list/describe EC2, S3 buckets, IAM users, and Lambda functions. Auth via STS-assumed role; no mutating tools.
Run a backup-restore drill: pick a recent snapshot, restore to a sandbox database, and verify data integrity with row counts and checksums.
Identify imports and module-init code that contribute to Cloudflare Worker cold starts and propose lazy-load rewrites.
Read a list of crontab specifications and detect overlapping execution windows that risk resource contention or duplicate work.
Find dangling DNS records (CNAMEs to dead hosts, A records for retired servers) and propose deletions with risk-of-takeover notes.
Convert a single-stage Dockerfile into a multi-stage build and verify the resulting image is at least 30% smaller than the original.