Product and engineering

The Cloudflare connector.

Zones, DNS records, analytics and Workers. Connect once with your own key. Every agent your team runs reads the same 4 tools under one permission model.

How access is governed

4

Read tools

Open by default. They run when called, and every call is logged with the endpoint, tool and capability.

0

Write tools

Cloudflare exposes no write tools. Nothing it does mutates external state.

0

Destructive tools

Cloudflare defines no destructive tools. Nothing here deletes data.

Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.

Every Cloudflare tool

4 tools, named as the agent sees them.

  • list_zonesread

    List the zones (domains) the API token can see. Start here: every other zone tool takes the `id` returned by this one as its `zone_id`.

  • get_zoneread

    Get one zone in full: status, plan, nameservers, and the original registrar/DNS host. Takes a `zone_id` from list_zones. Use it to confirm a domain is active and which plan gates a feature.

  • list_dns_recordsread

    List DNS records for a zone. Use this to answer "where does this hostname point" or "is this record proxied through Cloudflare". Takes a `zone_id` from list_zones.

  • get_zone_analyticsread

    Get traffic analytics for a zone: request, bandwidth, threat and pageview totals plus a timeseries. Takes a `zone_id` from list_zones. Cloudflare gates the retention window by plan, so a long `since` can be rejected on lower plans.

Use it from any agent

The same Cloudflare tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.

.mcp.json · works for Cursor and Claude Desktop too
{
  "mcpServers": {
    "growth": {
      "type": "http",
      "url": "https://app.notara.ai/mcp/g/acme/growth",
      "headers": {
        "Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

The URL and token are placeholders. Real endpoints are issued per group from the dashboard.

Setup

  1. 01

    Create a Cloudflare API Token in your Cloudflare account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.

  2. 02

    Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.

  3. 03

    The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.

More in product and engineering

LinearCursorSentryAsanaClickUpNotion

Connect Cloudflare once. Use it everywhere.

Use Notara directly, or bring us the workflow that needs to be redesigned and built.

Book a callSign in