Application Development
Cloudflare MCP connector
The Cloudflare connector lets Claude, ChatGPT, Cursor, or any MCP client look up your Cloudflare accounts, zones, members, roles, firewall rules, rule sets, WAF overrides, and audit logs through one governed Elaichi endpoint, inside each person's own access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
12 tools
How to connect
How to connect Cloudflare to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Cloudflare once
-
Open Connections, choose Add connection, and pick Cloudflare.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Cloudflare API key. One person generates a token in Cloudflare and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Cloudflare to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Cloudflare to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Cloudflare to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Cloudflare to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Cloudflare through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Security
Review firewall rules before a change window
Ask which firewall rules and rule sets are active on a zone and get them read back in plain language before anyone touches production.
-
IT
Check who still has access to Cloudflare
List every member across your Cloudflare accounts with their roles, then spot contractors and former staff who should no longer be there.
-
Compliance
Pull Cloudflare audit history for a review
When an auditor asks who changed what and when, have the agent read the Cloudflare audit log for the period and summarize it.
-
Support
Find the zone behind a customer domain
When a customer says their site is misbehaving, look up the zone it sits in and read its details without opening the Cloudflare dashboard.
-
Engineering
Compare rule sets across staging and production
Fetch the rule sets attached to two zones and ask where they differ before a release goes out.
-
Operations
Inventory every domain across accounts
List all zones across every Cloudflare account you manage for a quarterly ownership review, in one question instead of account by account.
Try asking
- “Which zones changed firewall rules in the last week?”
- “List members with admin roles on our production account.”
- “Show WAF overrides active across all Cloudflare zones.”
AI tools
Cloudflare tools for your AI agents
12 tools are ready to call through Elaichi's MCP endpoint the moment you connect Cloudflare, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Cloudflare gets you
6 screens from the product, each doing one job for your Cloudflare account.
The agent
Ask about zones, get answers from Cloudflare.
Plain language questions return live zones, firewall rules and members.
- zones
- firewall rules
- members
- rule sets
Ask Elaichi to work across your apps.
Which zones changed firewall rules in the last week?
List members with admin roles on our production account.
Show WAF overrides active across all Cloudflare zones.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Cloudflare.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
12 Cloudflare tools ready on connect.
Accounts, zones, members, roles, firewall rules and rule sets, no custom code.
- List all Cloudflare accounts
- Get single Cloudflare account by ID
- List all Cloudflare members
- Get single Cloudflare member by ID
ElaichiToolsToolboxes
Every team gets its own Cloudflare toolbox.
Curate one toolbox per team, from zone reads to WAF overrides.
- Platform
- Security
- SRE
- Engineering
ElaichiToolboxesShared connections
Teammates use Cloudflare without touching the token.
See who connected each account and which teams and members share it.
- Production
- Staging
- Security
- Marketing sites
ElaichiConnectionsAudit log
Every Cloudflare call has a name on it.
When, who, what happened, type and resource, appended and never edited.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a Cloudflare digest ships.
Fetch zones and firewall rules, group them, draft, approve, post back.
Cloudflare digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch zones
Cloudflare
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Cloudflare
Queued
Collections and dashboards
Cloudflare zone health, counted on a schedule.
Four metrics, 14 days of records created, split by team, no model involved.
Cloudflare health
Refreshed 4 minutes ago · every 15 minutes · from the zones collection
Zones
1,284 ↓ 12%
Firewall rules
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Zones created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Security 21%
Marketing sites 18%
FAQ
Frequently asked questions
How do I connect Cloudflare to Claude?
Connect Cloudflare in Elaichi first, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Cloudflare connects with an API key, so the sign-in step is pasting a key from your Cloudflare account into Elaichi. There is no OAuth application to register and no client ID or secret to generate.
Does Cloudflare work with ChatGPT and Cursor as well as Claude?
Yes. Once Cloudflare is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Cloudflare once and every client you use sees it.
What can an AI agent actually do with my Cloudflare data?
With the Cloudflare connector, an agent can list your accounts, zones, members and their roles, firewall rules, rule sets, WAF overrides, and audit logs, and look up any one of them by ID. That means you can ask in plain language which firewall rules protect a domain, who has access to an account, or what changed last week, and get an answer from live Cloudflare records. This connector reads Cloudflare; it does not change settings.
Does connecting Cloudflare give the AI access to every account and zone?
No. Everything the agent sees in Cloudflare follows the access of the person who signed in with their key, so it can only read the accounts and zones that person can already read in Cloudflare. Elaichi can narrow that further with restrictions per action, and it can never widen it beyond what Cloudflare itself allows.
Can I stop an agent from deleting or changing things in Cloudflare?
The Cloudflare connector in Elaichi only lists and looks up records such as zones, firewall rules, and members, so there is nothing here that deletes or changes a Cloudflare setting. On top of that, Elaichi restrictions work per action, so you can turn off any individual capability for a team. A blocked action is never advertised to Claude, ChatGPT, or Cursor, so no prompt can reach it.
What happens to a Cloudflare connection when someone leaves?
Offboarding a person in Elaichi ends their access to Cloudflare through Elaichi at once, across every client they used. A shared Cloudflare connection keeps working for everyone else on the team. If you want to remove Cloudflare entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Cloudflare in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.