Files
firefrost-operations-manual/docs/tasks/cloudflare-integration/README.md
Claude e886371177 task: add Cloudflare integration to Claude's toolbox
Identified during Firefrost Codex deployment - Claude needed to create
DNS record for codex.firefrostgaming.com but lacked Cloudflare access.

Task created for future implementation.

Signed-off-by: Chronicler #22
2026-02-22 22:47:27 +00:00

68 lines
1.5 KiB
Markdown

# Task: Add Cloudflare to Claude's Toolbox
**Created:** February 22, 2026
**Priority:** Medium
**Status:** IDENTIFIED
**Time Estimate:** 1-2 hours
---
## OBJECTIVE
Enable Claude to manage Cloudflare DNS records directly via API integration.
**Use case:** During Firefrost Codex deployment, needed to create DNS record for codex.firefrostgaming.com - Claude didn't have Cloudflare access.
---
## REQUIREMENTS
**API Access:**
- Generate new Cloudflare API token (will reroll for security)
- Store in Vaultwarden
- Configure appropriate permissions (DNS edit)
**Integration Method (TBD):**
- Option A: Custom skill in `/mnt/skills/user/cloudflare/`
- Option B: MCP server integration
- Option C: Simple bash wrapper script
**Capabilities Needed:**
- Create/update/delete DNS records (A, CNAME, TXT)
- List existing records
- Update proxy status (orange/gray cloud)
- Check zone/domain info
---
## PREREQUISITES
- [ ] Cloudflare account access
- [ ] Generate new API token with DNS edit permissions
- [ ] Store token in Vaultwarden
- [ ] Determine integration method (skill vs MCP)
---
## BENEFITS
- Claude can configure DNS during deployments
- No context switching for Michael
- Faster deployments
- Automation of DNS changes
---
## NOTES
**Security:**
- Token will be regenerated (don't use existing)
- Scope token to minimum required permissions
- Store securely in Vaultwarden
**Identified during:** Firefrost Codex migration (Task #9)
---
**Status:** Ready to build when time available