Kiwi for Cloudflare
Have the agent on a Kiwi step read and change Workers, DNS records and other Cloudflare settings, through the Cloudflare API MCP server.
- Your agent works in Cloudflare through its own connection. Kiwi does not call Cloudflare and never holds its credentials.
- A workflow skill can list Cloudflare among the tools it requires. When you supply your agent's available tools to a skill check and Cloudflare is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Cloudflare, with notes, under Connections and bind them to the steps that use them. The agent reads them with
list_connections. - The agent can report the tools and plugins it ran with, including its Cloudflare connection, with
report_configuration. - The agent submits links to its work in Cloudflare as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in Cloudflare
- Reach the whole Cloudflare API, more than 2,500 endpoints across DNS, Workers, R2 and Zero Trust, from one server.
- Search the Cloudflare developer documentation.
- Run the API calls the agent writes inside an isolated Dynamic Worker sandbox instead of loading one tool per endpoint.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to Cloudflare
Add the Cloudflare MCP server to your agent with this URL. The credentials stay with your agent.
https://mcp.cloudflare.com/mcpExample skill
Publish instructions like these as a workflow skill that lists Cloudflare among its required tools.
Read the Worker name and the target route from the step's inputs. Through Cloudflare, check the Worker's current version and the routes and DNS records that point to it. Upload the new Worker version as a preview; promoting it is for the Owner. Submit the preview URL and the version ID as the step's outputs. If the API returns a permission error, report a blocker.