Provides tools for interacting with a Cloudflare account via its API, including listing accounts and zones, reading and managing DNS records, purging cached content, and inventorying Worker scripts, KV namespaces, and R2 buckets.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
edgeport is a small doorway into a Cloudflare account. From one bin an agent can see which accounts and zones a token can reach, read and change DNS records, purge cached content, and inventory the account's Worker scripts, KV namespaces, and R2 buckets. It runs from the command line or as an MCP server for agents.
A Cloudflare API token is required. Put it in the
CLOUDFLARE_API_TOKEN environment variable; it is sent to the API as
a Bearer token and never appears in output. Account-scoped tools
(Worker scripts, KV, R2) take an account_id argument, and when that
is omitted they fall back to CLOUDFLARE_ACCOUNT_ID. When a required
variable is missing, the call fails with an error that names it.
This is a core subset of the Cloudflare API, not the whole surface: Workers bindings deep configuration, observability and Logpush, rulesets and firewall rules, Pages and deployments, Stream and Images, AI and Vectorize, and the hosted documentation search tool are out of scope.
npx @reneturcios/edgeport list-zonesOr run the container image:
docker run -i -e CLOUDFLARE_API_TOKEN ghcr.io/cloudcorprecords/edgeportThe container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
Related MCP server: Cloudflare Control
export CLOUDFLARE_API_TOKEN="your api token"
export CLOUDFLARE_ACCOUNT_ID="your account id" # optional fallback
edgeport list-accounts
edgeport list-zones --name example.com
edgeport get-zone --zone-id <zone id>
edgeport list-dns --zone-id <zone id> --type A
edgeport purge-cache --zone-id <zone id> --everything
edgeport list-workers
edgeport list-kv
edgeport list-r2
edgeport --versionExit codes: 0 on success, 1 when an API call fails (including a
missing CLOUDFLARE_API_TOKEN or a success: false envelope), 2
for usage errors.
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
npx -y @reneturcios/edgeport mcpMCP client configuration:
{
"mcpServers": {
"edgeport": {
"command": "npx",
"args": ["-y", "@reneturcios/edgeport", "mcp"],
"env": { "CLOUDFLARE_API_TOKEN": "your api token" }
}
}
}Tool | Input | What it returns |
|
| Accounts the token can access, from the envelope's result. |
|
| Zones, optionally filtered by account or name. |
|
| One zone's details. |
|
| DNS records in the zone. |
|
| The created record. |
|
| The updated record; only the fields given are sent. |
|
| The delete result. |
|
| The purge result for the zone. |
|
| Worker scripts in the account. |
|
| A shape summary only: content type, byte size, body present. The script body is never returned. |
|
| Workers KV namespaces in the account. |
|
| R2 buckets in the account. |
Every JSON response is unwrapped from Cloudflare's
{success, errors, result} envelope. A success: false envelope is
reported as a tool error carrying the API's own error entries.
npm install
npm run build # tsc -> dist/
npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures)
npm run dev # run the CLI from source via tsxMIT — see LICENSE.
This server cannot be deployed
Build, validate and deploy workflows as Cloudflare Workers in your own account, with approval.
The bridge from K2 agents through Wrangler to your master AI - safe, approval-gated Cloudflare ops.
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
Issue, rotate and revoke scoped API-key passes for 25+ providers — the agent never sees a real key
