---
title: "Kiwi for Cloudflare"
description: "Have the agent on a Kiwi step read and change Workers, DNS records and other Cloudflare settings, through the Cloudflare API MCP server."
canonical: "https://kiwiflow.io/integrations/cloudflare"
---

# 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

### 1. Connect your agent to Kiwi

Add Kiwi's hosted MCP server, `https://kiwiflow.io/mcp`, to your coding agent.

- [Coding agents](https://kiwiflow.io/integrations#agent)
- [Quickstart](https://docs.kiwiflow.io/quickstart#connect-your-agent)

### 2. 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/mcp
```

- [Cloudflare documentation](https://developers.cloudflare.com/agents/model-context-protocol/cloudflare/servers-for-cloudflare/)

### 3. Example 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.
```

## More deployment and hosting integrations

- [Kiwi for AWS](https://kiwiflow.io/integrations/aws.md): Have the agent on a Kiwi step call AWS APIs under the IAM permissions it signs in with and read the AWS documentation, through the AWS MCP Server.
- [Kiwi for Microsoft Azure](https://kiwiflow.io/integrations/microsoft-azure.md): Have the agent on a Kiwi step check a Microsoft Azure App Service app and query Azure Monitor, through the Azure MCP Server.
- [Kiwi for Google Cloud](https://kiwiflow.io/integrations/google-cloud.md): Have the agent on a Kiwi step deploy a container to Cloud Run and read the service back, through Google Cloud's remote MCP server for Cloud Run.
- [Kiwi for Vercel](https://kiwiflow.io/integrations/vercel.md): Have the agent on a Kiwi step check a Vercel preview deployment and read its runtime logs, through Vercel's MCP server.
- [Kiwi for DigitalOcean](https://kiwiflow.io/integrations/digitalocean.md): Have the agent on a Kiwi step update a DigitalOcean App Platform app and follow its deployment, through DigitalOcean's MCP server.
- [Kiwi for Supabase](https://kiwiflow.io/integrations/supabase.md): Have the agent on a Kiwi step apply a database migration to a Supabase project and run the advisors afterwards, through Supabase's MCP server.
- [Kiwi for Netlify](https://kiwiflow.io/integrations/netlify.md): Have the agent on a Kiwi step deploy a site to Netlify and set its environment variables, through Netlify's MCP server.
- [Kiwi for Heroku](https://kiwiflow.io/integrations/heroku.md): Have the agent on a Kiwi step check a Heroku app's dynos, logs and Postgres database, through Heroku's MCP server.
- [Kiwi for Fly.io](https://kiwiflow.io/integrations/fly-io.md): Have the agent on a Kiwi step check a Fly.io app's status, Machines and logs, through the MCP server in Fly.io's flyctl CLI.
- [Kiwi for Render](https://kiwiflow.io/integrations/render.md): Have the agent on a Kiwi step trigger a Render deploy, filter the service's logs and read its metrics, through Render's MCP server.
- [Kiwi for Railway](https://kiwiflow.io/integrations/railway.md): Have the agent on a Kiwi step redeploy a Railway service in a non-production environment, through Railway's MCP server.

- [Get started](https://kiwiflow.io/get-started)
- [Read the setup guide](https://docs.kiwiflow.io/other-tools)