Back to Browse

Cloudflare Tools MCP Server

Cloud & DevOpsLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

Cloudflare tools for coding agents: zones, DNS, analytics, Workers, Pages, storage and tunnels.

About

Cloudflare tools for coding agents: zones, DNS, analytics, Workers, Pages, storage and tunnels.

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (2 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (16/16 approved); 4 highly-trusted packages.

10 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "cloudflare-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@craftsamo/cloudflare-tools@0.13.0"
      ]
    }
  }
}

Some servers take additional arguments. See the repository for details.

Documentation

View on GitHub

From the project's GitHub README.

cloudflare-tools

Cloudflare tools for coding agents: zones, DNS, analytics, Workers, Pages, storage and tunnels.

HarnessDeliveryPinned by
OpenCode V2native plugin (npm package, with skills)the version in the package
OpenCode V1native plugin (npm package, no skills)the version in the package
Claude Codeplugin: MCP server and skillsthe release tag, as the ref
Codexplugin: MCP server and skillsthe release tag, as the ref
Grok Buildplugin: MCP server and skillsthe release tag, as @ref
Antigravityplugin: MCP server and skillsthe release tag's tree URL
Hermes Agentnative plugin (Python, calls the command line)the release commit, as the SHA
other MCP hostMCP server from npmthe version in the package

The tools need Node.js 24 or later. docs/conventions.md describes how the tools are named and how they behave.

Install

Install from a release, never from the default branch: a release is a tag whose commit carries the built dist/, and the default branch does not. In the commands below, <version> is a release's version (1.2.3) and <sha> is the commit its tag names:

gh api repos/craft-agent/cloudflare-tools/commits/v<version> --jq .sha

OpenCode

OpenCode V2 takes the package and its options in opencode.json:

{
  "plugins": [{ "package": "@craftsamo/cloudflare-tools@<version>", "options": { "read_only": false } }],
  "permissions": [{ "action": "cloudflare_*", "resource": "*", "effect": "ask" }]
}

OpenCode V1 takes the package as a string, or as a pair with its options:

{
  "plugin": [["@craftsamo/cloudflare-tools@<version>", { "read_only": false }]],
  "permission": { "cloudflare_*": "ask" }
}

OpenCode allows any action no rule names, so the plugin's request is granted silently unless a rule says ask. Read tools never ask, so the cloudflare_* glob is safe.

The options are the settings. A toolset that is off by default is turned on by listing it in toolsets with the ones to keep, for example "options": { "toolsets": ["account", "zones", "dns", "workers", "pages", "email"] }.

V1 registers no skills. Unpack the package and copy its skills/* folders into ~/.config/opencode/skills/:

npm pack @craftsamo/cloudflare-tools@<version>
tar -xzf craftsamo-cloudflare-tools-<version>.tgz
mkdir -p ~/.config/opencode/skills
cp -r package/skills/* ~/.config/opencode/skills/
rm -rf package craftsamo-cloudflare-tools-<version>.tgz

Claude Code

claude plugin marketplace add craft-agent/plugins
claude plugin install cloudflare-tools@craft-agent

craft-agent/plugins lists every craft-agent package at its latest release. To pin this package to a release instead, add its own marketplace at the tag, and do not install it from both:

claude plugin marketplace add craft-agent/cloudflare-tools#v<version>
claude plugin install cloudflare-tools@cloudflare-tools

If you added this repository as the craft-agent marketplace before, remove it first: claude plugin marketplace remove craft-agent.

Codex

codex plugin marketplace add craft-agent/plugins
codex plugin add cloudflare-tools@craft-agent

craft-agent/plugins lists every craft-agent package at its latest release. To pin this package to a release instead, add its own marketplace at the tag, and do not install it from both:

codex plugin marketplace add craft-agent/cloudflare-tools --ref v<version>
codex plugin add cloudflare-tools@cloudflare-tools

If you added this repository as the craft-agent marketplace before, remove it first: codex plugin marketplace remove craft-agent.

Codex turns - into _ in server names, so it shows the tools as mcp__cloudflare_tools__cloudflare_*. It starts the MCP server in the plugin's install directory and passes no roots, so the server takes each call's directory from what Codex sends with the call: its sandbox state, which the server asks for, else the one workspace it names.

The plugin declares default_tools_approval_mode = "writes": Codex asks before every tool not marked read-only. A user's [plugins."<plugin>".mcp_servers.<server>] setting can only tighten it. Setting auto there yields prompt (reads asked too), since Codex treats auto and writes as incomparable.

Grok Build

grok plugin install craft-agent/cloudflare-tools@v<version> --trust

Grok starts the MCP server in the session's working directory.

Antigravity

Install from the tree of the release tag, never from the default branch, which has no built dist/; Antigravity clones the tag into ~/.gemini/config/plugins/cloudflare-tools.

agy plugin install https://github.com/craft-agent/cloudflare-tools/tree/v<version>

Hermes Agent

Hermes installs a commit, not a tag, and the plugin installs disabled:

hermes plugins install craft-agent/cloudflare-tools --ref <sha>
hermes plugins enable cloudflare-tools

Hermes scans a plugin when it installs it. From v0.7.0 the verdict is caution: the tunnel tools name the token permission Account → Cloudflare One Connector: cloudflared, and Hermes rates the word as a tunneling service. hermes plugins install then asks before installing; where it cannot ask (no terminal), add --force, which overrides a caution verdict and no other.

If a Hermes gateway is already running, restart it (hermes gateway restart) to load the plugin.

The plugin runs the Node it found when Hermes started. If a version manager removes that version while Hermes runs, a call looks for Node again; when it finds none, restart Hermes from a shell where node runs.

When the package's writes depend on another Hermes plugin, such as a guard that blocks writes no one is there to approve, name it in require_plugins. Hermes keeps loading this plugin when that one fails to import or register, and treats a manifest's requires_plugins as advisory. With the setting, while a named plugin is not loaded, every write is refused before it is approved, even under --yolo, approvals.mode: off or a remembered answer, naming the plugin that is missing. Reads still run.

plugins:
  entries:
    cloudflare-tools:
      settings:
        require_plugins: [write-guard]

Any other MCP host

Add the server to the host's MCP configuration. Flags go in args:

{
  "mcpServers": {
    "cloudflare-tools": {
      "command": "npx",
      "args": ["-y", "@craftsamo/cloudflare-tools@<version>", "--read-only"]
    }
  }
}

Tools and skills

Confirmations described below apply to attended runs. With unattended on, a write runs without asking only under a grant that covers it; otherwise it is refused. See Writes no one is there to approve.

Each toolset comes with a skill that tells an agent how to use its tools. A skill names its toolset under metadata in its frontmatter (metadata: { toolset: dns }, written as a block). OpenCode V2 and Hermes register it only when the settings register at least one of that toolset's tools, so a profile with the toolset off, or with all its tools removed, does not see it; a skill without a toolset is always registered. Claude Code, Codex, Grok Build and Antigravity install the skill folder whole and pass the settings only to the MCP server, so they list every skill whatever the settings select. OpenCode V1 registers no skills, and its copied skills are all listed too.

Account (account)

Account credentials, token verification, and audit logs.

ToolWhat it doesClass
cloudflare_account_readview account details and token status, list configured accounts, or query audit logsread

The skill is cloudflare-account, shown as cloudflare-tools:cloudflare-account in Claude Code and cloudflare-tools:account in Hermes.

Zones (zones)

Zone lookup, settings (read and change), Universal SSL, certificates, and DNSSEC.

ToolWhat it doesClass
cloudflare_zone_readlist zones, view details, read settings, Universal ssl status, or dnssecread
cloudflare_zone_setting_editchange 1–20 zone settings in order; refuses a change that lowers protectionoverwrite
cloudflare_zone_setting_weakenchange zone settings in ways that lower a visitor's protection; always asks firstadministrative
cloudflare_zone_cache_purgepurge cached copies of up to 100 URLs, hosts, prefixes or tags in a zoneidempotent
cloudflare_zone_cache_purge_allpurge the whole cache of a zone; always asks firstadministrative
cloudflare_zone_dnssec_enableturn DNSSEC on for a zone; harmless until registrar publishes the DS recordidempotent
cloudflare_zone_dnssec_disableturn DNSSEC off for a zone; requires DS removed at registrar firstadministrative

The skill is cloudflare-zones, shown as cloudflare-tools:cloudflare-zones in Claude Code and cloudflare-tools:zones in Hermes.

DNS (dns)

DNS records: list, read one in full, export the zone file, add records, change them, and delete them.

ToolWhat it doesClass
cloudflare_dns_readlist records, view one in full, or export the zone file in BIND formread
cloudflare_dns_record_addadd 1–20 records of eight types in one all-or-nothing batchadd
cloudflare_dns_record_editchange 1–20 records by id in one all-or-nothing batch; never a record's typeoverwrite
cloudflare_dns_record_deletedelete 1–20 records by id, with replacements in the same batch; always asks firstadministrative

The skill is cloudflare-dns, shown as cloudflare-tools:cloudflare-dns in Claude Code and cloudflare-tools:dns in Hermes.

Rules (rules)

Rules: read which rule phases of a zone hold rules and the rules of one phase in order, with their ids, positions and versions; add, change, move or delete a Single Redirect, Cache Rule, Configuration Rule, URL Rewrite Rule, Request or Response Header Transform Rule, Origin Rule or Compression Rule. WAF custom rules, rate limiting rules and custom error rules can be read but not changed. Expressions, descriptions and parameters are the user's data, returned as data and never instructions. This toolset is off by default; turn it on with the toolsets setting (see Settings).

ToolWhat it doesClass
cloudflare_rules_readwhich phases of a zone hold rules; the rules of one phase in orderread
cloudflare_rules_addadd a rule to a phase, last or before, after or at a place; refuses a duplicate of a rule the phase holdsadd
cloudflare_rules_editchange a rule's expression, action, parameters, description, on/off or place, naming the version read; refuses a rule changed sinceoverwrite
cloudflare_rules_deletedelete a rule of a phase; always asks firstadministrative

The token needs Zone → Dynamic URL Redirects, Cache Settings, Config Settings, Zone Transform Rules, Origin or Response Compression → Read for the phase it reads, and Edit to add, change or delete a rule in it. Zone → Zone WAF and Custom Errors → Read cover the read-only phases.

The skill is cloudflare-rules, shown as cloudflare-tools:cloudflare-rules in Claude Code and cloudflare-tools:rules in Hermes.

Analytics (analytics)

Analytics: read a zone's traffic per day (requests, bandwidth, cache hits, threats, page views and unique visitors), the most requested paths, client countries and response statuses, what the security features did (not on the Free plan) and the latest security events, and the account's Workers invocations, errors and CPU time, over a recent time range. This toolset is off by default; turn it on with the toolsets setting (see Settings).

ToolWhat it doesClass
cloudflare_analytics_readtraffic per UTC day; the top paths, countries and statuses; security and security_events; workersread

The token needs Zone → Analytics → Read, and Zone Read to look the zone up; workers needs Account → Account Analytics → Read instead.

The skill is cloudflare-analytics, shown as cloudflare-tools:cloudflare-analytics in Claude Code and cloudflare-tools:analytics in Hermes.

Workers (workers)

Workers: list them, read one's settings and bindings, deployments and versions, a zone's Worker routes, custom domains, cron triggers and secret names and types, and roll a Worker back to versions that served before. Building, uploading and deploying new code stay with Wrangler; routes, custom domains and cron triggers are read here and changed in wrangler.toml.

ToolWhat it doesClass
cloudflare_workers_readlist, view, deployments, versions, routes, domains, schedules, secrets (names only)read
cloudflare_workers_rollbackroll a Worker back to versions that served before; always asks firstadministrative

The token needs Workers Scripts Read; routes also needs Workers Routes Read; routes, and domains with zone, need Zone Read to look the zone up. The rollback needs Workers Scripts Write.

The skill is cloudflare-workers, shown as cloudflare-tools:cloudflare-workers in Claude Code and cloudflare-tools:workers in Hermes.

Pages (pages)

Pages: list projects, read their build settings, environment variable names and bindings, production and preview deployments, including which one is live, a build's logs, and custom domains; switch a project's production back or forward to a deployment that built successfully; and add or remove its custom domains. Building and deploying new code stay with Git and Wrangler; the DNS records of a custom domain stay with the DNS tools.

ToolWhat it doesClass
cloudflare_pages_readlist projects, view one, its deployments, a build's logs, custom domainsread
cloudflare_pages_rollbackswitch production to a deployment that built successfully; always asks firstadministrative
cloudflare_pages_domain_addadd a custom domain to a project, creating no DNS record; always asks firstadministrative
cloudflare_pages_domain_removeremove a custom domain from a project, deleting no DNS record; always asks firstadministrative

The token needs the Pages Read permission. The writes need Pages Write, and the DNS lookups of the domain tools need Zone Read and DNS Read.

The skill is cloudflare-pages, shown as cloudflare-tools:cloudflare-pages in Claude Code and cloudflare-tools:pages in Hermes.

Storage (storage)

Storage: list an account's R2 buckets and a bucket's objects and folders by name, size and date, and read whether a bucket is public (its r2.dev domain and custom domains), its CORS rules and the lifecycle rules that delete its objects; list Workers KV namespaces and their key names; list D1 databases and read one's size and schema; create an empty bucket, namespace or database, and delete one that is proven empty. An object's body, a KV value and a table's rows are never read, the D1 schema comes from one fixed statement, and only the default jurisdiction is listed. Cloudflare deletes a KV namespace or D1 database with its contents, so the delete tool proves the store empty first; emptying a store stays with the user. This toolset is off by default; turn it on with the toolsets setting (see Settings).

ToolWhat it doesClass
cloudflare_storage_readR2 buckets, a bucket's details, its objects; KV namespaces, their keys; D1 databases, a database's schemaread
cloudflare_storage_createcreate an empty R2 bucket, KV namespace or D1 database from a nameadd
cloudflare_storage_deletedelete a bucket, namespace or database only when it is proven empty; always asks firstadministrative

The token needs Account → Workers R2 Storage → Read, Workers KV Storage → Read or D1 → Read, for the store it reads; creating and deleting need the same permission's Edit.

The skill is cloudflare-storage, shown as cloudflare-tools:cloudflare-storage in Claude Code and cloudflare-tools:storage in Hermes.

Tunnels (tunnels)

Tunnels: list an account's Cloudflare Tunnels by name, status and connection times, and read one tunnel's active connectors, edge connections, colos and public-hostname ingress routing rules. A tunnel's run token is never exposed, connectors' internal ids and origin IP addresses are never read, and deleted tunnels are left out. For locally managed tunnels, ingress rules are kept on the host and cannot be read here. A hostname can be published through a dashboard-managed tunnel to a local service: the tool adds the rule and the proxied CNAME it needs, refuses a hostname that has other DNS records, and always asks first. Another tool changes the service a published hostname goes to, and one withdraws a hostname, deleting its CNAME to the tunnel when no other rule uses it and never touching other records; both always ask first. This toolset is off by default; turn it on with the toolsets setting (see Settings).

ToolWhat it doesClass
cloudflare_tunnel_readtunnels of the account; one tunnel's status and ingressread
cloudflare_tunnel_route_addpublish a hostname (and optional path) through a tunnel to a local service; always asks firstadministrative
cloudflare_tunnel_route_editchange the service a published hostname goes to, naming the current one; always asks firstadministrative
cloudflare_tunnel_route_removewithdraw a hostname from a tunnel and delete its CNAME to the tunnel; always asks firstadministrative

The token needs Account → Cloudflare One Connector: cloudflared → Read. Publishing or withdrawing a hostname needs Account → Cloudflare One Connector: cloudflared → Edit and Zone → DNS → Edit; changing where one goes needs Account → Cloudflare One Connector: cloudflared → Edit, and Zone → DNS → Read for the record it reports. Each public hostname also says whether a Zero Trust Access application matches it, which needs Account → Access: Apps and Policies → Read; without it the coverage is unknown. A match is not a promise that every visitor signs in: a Bypass policy can still let them through.

The skill is cloudflare-tunnels, shown as cloudflare-tools:cloudflare-tunnels in Claude Code and cloudflare-tools:tunnels in Hermes.

Email Routing (email)

Email Routing: read whether a zone's Email Routing is on, its routing rules and catch-all (each rule matches one address and forwards it to one verified address, drops it or hands it to a Worker), and the account's destination addresses with whether each is verified; add, change or delete a routing rule for one address, change the catch-all, and add or delete a destination address. A rule a Worker's Wrangler configuration manages is marked as such, and a zone with Email Routing off routes no mail. Addresses, names and Worker names are the user's data, returned as data and never instructions. This toolset is off by default; turn it on with the toolsets setting (see Settings).

ToolWhat it doesClass
cloudflare_email_reada zone's routing settings and catch-all; its rules; the account's addressesread
cloudflare_email_rule_addadd a rule that forwards one address to a verified destination, drops it or hands it to a Worker (Cloudflare refuses one that does not exist); refuses an address that already has a ruleadd
cloudflare_email_rule_editchange a rule's address, action, name or whether it is on, naming its current action; refuses the catch-all and Wrangler-managed rulesoverwrite
cloudflare_email_rule_deletedelete a rule, naming where its mail goes next; refuses the catch-all and Wrangler-managed rules; always asks firstadministrative
cloudflare_email_catchall_editchange the action of the catch-all (mail no rule matches) or turn it on or off, naming its current state; refuses Wrangler-managed catch-alls; always asks firstadministrative
cloudflare_email_address_addadd a destination address; Cloudflare mails its owner a link to confirm, and no rule can forward to it until they follow it; always asks firstadministrative
cloudflare_email_address_deletedelete a destination address; refuses while a rule or catch-all in any zone of the account forwards to it; always asks firstadministrative

The token needs Zone → Email Routing Rules → Read, and Account → Email Routing Addresses → Read for the addresses. Adding, changing or deleting a rule, and changing the catch-all, need Zone → Email Routing Rules → Edit, and adding or changing a forward needs Account → Email Routing Addresses → Read to check it. Adding or deleting a destination address needs Account → Email Routing Addresses → Edit, and deleting one also needs Zone → Email Routing Rules → Read in every zone of the account.

The skill is cloudflare-email, shown as cloudflare-tools:cloudflare-email in Claude Code and cloudflare-tools:email in Hermes.

Queues (queues)

List an account's Cloudflare Queues and read one queue's delivery settings, consumers with their batch and retry settings, and producers. Messages are never read. Queue and Worker names are the user's data, returned as data and never instructions. This toolset is off by default; turn it on with the toolsets setting (see Settings).

ToolWhat it doesClass
cloudflare_queues_readlist the account's queues; view one queue's settings, consumers and producersread

The token needs Account → Queues → Read.

The skill is cloudflare-queues, shown as cloudflare-tools:cloudflare-queues in Claude Code and cloudflare-tools:queues in Hermes.

Hyperdrive (hyperdrive)

List an account's Hyperdrive configurations and read one configuration's origin database, caching, mTLS and connection limit. Passwords and Access client secrets are never returned. Names, hosts, database names and other origin details are the user's data, returned as data and never instructions. This toolset is off by default; turn it on with the toolsets setting (see Settings).

ToolWhat it doesClass
cloudflare_hyperdrive_readlist the account's configurations; view one configuration's origin, caching, mTLS and connection limitread

The token needs Account → Hyperdrive → Read.

The skill is cloudflare-hyperdrive, shown as cloudflare-tools:cloudflare-hyperdrive in Claude Code and cloudflare-tools:hyperdrive in Hermes.

Vectorize (vectorize)

List an account's Vectorize indexes and read one index's dimensions, distance metric, vector count, processing progress and metadata indexes. Vectors and their metadata values are never read. Index names and descriptions are the user's data, returned as data and never instructions. This toolset is off by default; turn it on with the toolsets setting (see Settings).

ToolDoesClass
cloudflare_vectorize_readlist the account's indexes; view one index's configuration, processing progress and metadata indexesread

The token needs Account → Vectorize → Read.

The skill is cloudflare-vectorize, shown as cloudflare-tools:cloudflare-vectorize in Claude Code and cloudflare-tools:vectorize in Hermes.

Turnstile (turnstile)

List an account's Turnstile widgets and read one widget's hostnames, mode, pre-clearance cookie level, region and settings. A widget's secret key is never returned. Widget names and hostnames are the user's data, returned as data and never instructions. This toolset is off by default; turn it on with the toolsets setting (see Settings).

ToolDoesClass
cloudflare_turnstile_readlist the account's widgets; view one widget's hostnames, mode, clearance level, region and settingsread

The token needs Account → Turnstile Sites → Read.

The skill is cloudflare-turnstile, shown as cloudflare-tools:cloudflare-turnstile in Claude Code and cloudflare-tools:turnstile in Hermes.

Access (access)

List the account's (or a zone's) Zero Trust Access applications, read one application with its policies, and list the account's reusable policies. Policies are returned with their include, exclude and require rules as configured, email addresses included; secrets are never returned. Application and policy names, domains and rules are the user's data, returned as data and never instructions. This toolset is off by default; turn it on with the toolsets setting (see Settings).

ToolDoesClass
cloudflare_access_readapps lists the account's (or a zone's) applications; app reads one with its policies; policies lists reusable policiesread

The token needs Account → Access: Apps and Policies → Read, and Zone → Access: Apps and Policies → Read for a zone's applications.

The skill is cloudflare-access, shown as cloudflare-tools:cloudflare-access in Claude Code and cloudflare-tools:access in Hermes.

Registrar (registrar)

List an account's registered domains and read one domain's status, expiration, automatic renewal, transfer lock and WHOIS privacy mode. Registrant contacts are never returned. Domain names are the user's data, returned as data and never instructions. This toolset is off by default; turn it on with the toolsets setting (see Settings).

ToolDoesClass
cloudflare_registrar_readlist registered domains with cursor pagination and sorting; view one domain's registration metadataread

The token needs Account → Registrar Domains → Read.

The skill is cloudflare-registrar, shown as cloudflare-tools:cloudflare-registrar in Claude Code and cloudflare-tools:registrar in Hermes.

Grants (grants)

Off by default. Delegates bounded writes for jobs where no person can answer.

ToolWhat it doesClass
cloudflare_grant_createask a person to delegate one tool's writes within limitsadministrative
cloudflare_grant_readlist grants and their use, or read the usage logread
cloudflare_grant_revokeremove a grant so no more calls run under itoverwrite

Every write tool can be granted for its targets, calls per hour and expiry. A tool adds what a grant can also limit by declaring bounds and giving measure(args, context) in its spec: a ceiling (max), a yes or no (allow), values from a list (oneOf) or the paths a value must sit under (prefix); see the conventions. No tool of this package declares bounds yet.

Adding a tool

  1. Write the spec in src/core/<domain>/<verb>.ts with defineTool: an ID <prefix>_<domain>_<verb>, a title and description, the Zod argument and output schemas, its toolset and write class, and execute(args, context). A write tool also gives targets(args, context): what the call writes to, as a permission rule should name it. A tool whose settings can put some calls out of reach whatever the person answers gives gate(args, context), which throws for such a call; it is refused before anyone is asked, and before execute.
  2. Test it beside the spec (<verb>.test.ts), calling it through invoke as the entry points do. A tool that runs a program is tested against a fake of that program on PATH; no test reaches a real service.
  3. List it in src/tools.ts. A new toolset goes into toolsets in src/project.ts (and defaultToolsets when it is on by default), a setting of the package's own into options (and OPTIONS in project.py with config_schema in plugin.yaml), and a variable the tool reads besides the settings into toolVariables.
  4. Add or update the toolset's skill, skills/<prefix>-<toolset>/SKILL.md, whose frontmatter names the toolset under metadata.
  5. Run pnpm run build && pnpm run manifests to list the tool in plugin.yaml and its variables in Codex's manifest, then describe it under "Tools and skills".

docs/conventions.md has the rules each step follows.

A package declares each option as text, boolean, number, list, path or paths, or as an object with type and optional bounds. For example, in src/project.ts:

options: {
  notes_dir: "path",
  note_limit: { type: "number", integer: true, min: 1, max: 50 },
}

integer: true requires a whole number; min and max bound a number or count a list or paths value's items. An object with only type means the same as the type alone. Hermes's OPTIONS mirrors the declarations on one line, with double quotes and Python's True for integer:

OPTIONS: dict[str, str | dict[str, object]] = {"notes_dir": "path", "note_limit": {"type": "number", "integer": True, "min": 1, "max": 50}}

Reads and writes

Every read tool is named <prefix>_<domain>_read. Reads can run unasked; in attended runs, writes are confirmed by the harness. With unattended on, writes instead need a covering grant, as described below.

HarnessReads without asking
OpenCodealways; the plugin asks only before a write
Claude Codethe rule mcp__plugin_cloudflare-tools_cloudflare-tools__*_read in permissions.allow of ~/.claude/settings.json
Codexalways; Codex runs tools that declare readOnlyHint unasked, as the read tools do
Grok Buildgrok --allow 'MCPTool(cloudflare-tools__*_read)' --allow 'MCPTool(cloudflare_*_read)' (both rules; see below)
Antigravitythe rule mcp(cloudflare-tools_cloudflare-tools/<tool id>) in permissions.allow, one for each read tool
Hermesalways; the plugin asks only before a write

Where a write is asked about, and where it is not:

  • OpenCode grants any action no rule names, so a write runs unasked unless a rule asks for it: add the cloudflare_* rule shown under OpenCode.
  • Codex asks before every write because of the plugin's approval mode. Under codex exec it refuses with "MCP tool call requires approval, but approval policy is never". For bounded jobs, see Writes no one is there to approve.
  • Grok Build under grok -p refuses a write it cannot ask about, unless it is allowed beforehand.
  • Grok Build calls the plugin's tools through its use_tool tool, and the agent often names a tool without its server first. Grok checks the rules against the name as given, so the server-qualified rule alone does not match that first call. The second rule matches the short name; a write still matches neither.
  • Antigravity asks before any MCP tool no rule allows, reads included, and names the plugin's server cloudflare-tools_cloudflare-tools (plugin, then server). agy -p refuses a tool it cannot ask about.
  • Hermes hermes chat -q refuses a write it cannot ask about; hermes -z and --yolo skip approval, so writes then run unasked. For bounded jobs, see Writes no one is there to approve.

A call a tool's gate refuses never runs, whatever the answer. OpenCode and Hermes refuse it before they ask, so no prompt shows it; Hermes blocks it with the tool's error. Claude Code, Codex, Grok Build and Antigravity draw their own prompt before the MCP server sees the call, so they may still ask about it; the server then refuses it.

Writes no one is there to approve

A grant limits a job's writes to one tool, for at most 90 days. The person decides the rest: the targets (named ones, or * for any), the bounds the tool declares (one left out is no limit) and the calls per hour (left out, any number). Every call made under a grant is logged. A grant never overrides the host's permissions. The conventions give the contract.

Documentation truncated — see the full README on GitHub.

Reviews

No reviews yet

Be the first to review this server!