Product and engineering

The Netlify connector.

Sites, deploys and form submissions. Connect once with your own key. Every agent your team runs reads the same 5 tools under one permission model.

How access is governed

5

Read tools

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

0

Write tools

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

0

Destructive tools

Netlify 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 Netlify tool

5 tools, named as the agent sees them.

  • list_sitesread

    List Netlify sites the token can access. Start here — the returned site `id` is what get_site, list_deploys and list_form_submissions take.

  • get_siteread

    Get one site in full, including its build settings and published deploy. Takes the site `id` from list_sites.

  • list_deploysread

    List a site’s deploys, newest first — use this to check whether the last build succeeded. Takes the site `id` from list_sites; the returned deploy `id` feeds get_deploy.

  • get_deployread

    Get one deploy in full, including its error_message when the build failed. Takes the deploy `id` from list_deploys (this route is site-independent).

  • list_form_submissionsread

    List the form submissions captured by a site — use this to read contact-form or signup entries. Takes the site `id` from list_sites.

Use it from any agent

The same Netlify 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 Netlify Personal Access Token in your Netlify 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 Netlify once. Use it everywhere.

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

Book a callSign in