Netlify

Developer ToolsPublisher: Netlify

Route Netlify MCP traffic through Formal to control and log what AI agents do in Netlify:

Block tools you don’t want agents to call, such as set_environment_variable.
Mask sensitive data in tool results, such as emails in list_sites responses.
Keep credentials at the Connector, so users and agents never see Netlify tokens.
Log every tool call with the user, the MCP client and its parameters.

0. Prepare your Connector

The Connector needs an MCP listener and a hostname with wildcard DNS and TLS. Set them up once by following Deploy the Connector. Every MCP server reuses them.

1. Add Netlify MCP server to your Resources

UI
Terraform
Pulumi
API

Open the Admin Catalog and click Add MCP.
Select the Netlify template.
Enter a DNS-label Name, such as netlify.
Choose the Space containing your Connector, such as default.
Configure upstream authentication as described below, then save.

If no Connector is in the selected Space, the Configuration tab shows MCP clients can’t connect directly yet. The reason reads: No Connector is in this server's Space.

Set space_id to the ID of the Space containing your Connector.

resource "formal_resource" "netlify" {
  name                    = "netlify"
  technology              = "mcp"
  hostname                = "netlify-mcp.netlify.app"
  space_id                = "<SPACE_ID>"
  native_users_v3_enabled = true
  port                    = 443
  tags = {
    "mcp-endpoint" = "/mcp"
  }
}

resource "formal_resource_oauth_settings" "netlify" {
  resource_id = formal_resource.netlify.id
}

Set spaceId to the ID of the Space containing your Connector.

import * as formal from "@formalco/pulumi";

const resource = new formal.Resource("mcp", {
  name: "netlify",
  technology: "mcp",
  hostname: "netlify-mcp.netlify.app",
  port: 443,
  spaceId: "<SPACE_ID>",
  tags: { "mcp-endpoint": "/mcp" },
  nativeUsersV3Enabled: true,
});

new formal.ResourceOauthSettings("mcpOAuth", {
  resourceId: resource.id,
});

Create a Resource with the MCP endpoint and its Space ID.

export FORMAL_API_KEY="<YOUR_API_KEY>"
RESOURCE_RESPONSE=$(curl --fail --silent --show-error \
  --request POST \
  https://api.formal.ai/core.v1.ResourceService/CreateResource \
  --header "x-api-key: ${FORMAL_API_KEY}" \
  --header "Content-Type: application/json" \
  --data-binary @- <<JSON
  {
    "name": "netlify",
    "hostname": "netlify-mcp.netlify.app",
    "port": 443,
    "technology": "mcp",
    "spaceId": "<SPACE_ID>",
    "tags": [
      {
        "key": "mcp-endpoint",
        "value": "/mcp"
      }
    ]
  }
JSON
)
RESOURCE_ID=$(printf '%s' "${RESOURCE_RESPONSE}" | jq -r '.resource.id')
curl --fail --silent --show-error \
  --request POST \
  https://api.formal.ai/core.v1.ResourceService/CreateResourceOAuthSettings \
  --header "x-api-key: ${FORMAL_API_KEY}" \
  --header "Content-Type: application/json" \
  --data-binary @- <<JSON
  {
    "resourceId": "${RESOURCE_ID}"
  }
JSON

2. Setup Authentication

Linked Accounts (Recommended)
Shared Credentials
Pass Through

Each user links their own Netlify account once in the Employee Catalog, and the Connector sends that user’s token to Netlify.

Linked Accounts selected under How does Formal authenticate to this resource?

Under OAuth app, keep Formal’s App.

Formal’s App (default)

Formal has a registered OAuth app with Netlify, so you register nothing. Users see Formal on Netlify’s consent screen.

3. Route Endpoint traffic

Auth is managed at the Connector level when you use Linked Accounts or Shared Credentials, so the Endpoint needs to forward the MCP traffic to it. Laptops and VMs with the Formal Endpoint keep using https://netlify-mcp.netlify.app/mcp, and a network rule sends that traffic to the Connector.

UI
Terraform
Pulumi
API

Go to Network Rules and create a rule named netlify-mcp.
Paste this expression, set the rule to Active, then save:

{
  "condition": {
    "pre_tcp": process.is_agent,
    // Every MCP server added to Formal: process.is_agent && resource.technology == "mcp"
    "pre_tls": process.is_agent && hostname == "netlify-mcp.netlify.app",
    "post_tls": true
  },
  "outputs": {
    "forward_to_connector": true
  }
}

resource "formal_network_rule" "netlify_mcp" {
  name        = "netlify-mcp"
  description = "Forward Netlify MCP traffic from agents to the Connector"
  status      = "active"

  # Every MCP server added to Formal: set pre_tls to process.is_agent && resource.technology == "mcp"
  cel_expression = <<-EOT
    {
      "condition": {
        "pre_tcp": process.is_agent,
        "pre_tls": process.is_agent && hostname == "netlify-mcp.netlify.app",
        "post_tls": true
      },
      "outputs": {
        "forward_to_connector": true
      }
    }
  EOT
}

import * as formal from "@formalco/pulumi";

new formal.NetworkRule("netlifyMcp", {
  name: "netlify-mcp",
  description: "Forward Netlify MCP traffic from agents to the Connector",
  status: "active",
  // Every MCP server added to Formal: set pre_tls to process.is_agent && resource.technology == "mcp"
  celExpression: `
    {
      "condition": {
        "pre_tcp": process.is_agent,
        "pre_tls": process.is_agent && hostname == "netlify-mcp.netlify.app",
        "post_tls": true
      },
      "outputs": {
        "forward_to_connector": true
      }
    }
  `,
});

export FORMAL_API_KEY="<YOUR_API_KEY>"
# Every MCP server added to Formal: set pre_tls to process.is_agent && resource.technology == "mcp"
CEL_EXPRESSION=$(cat <<'CEL'
{
  "condition": {
    "pre_tcp": process.is_agent,
    "pre_tls": process.is_agent && hostname == "netlify-mcp.netlify.app",
    "post_tls": true
  },
  "outputs": {
    "forward_to_connector": true
  }
}
CEL
)
jq -n --arg cel "${CEL_EXPRESSION}" '{
  name: "netlify-mcp",
  description: "Forward Netlify MCP traffic from agents to the Connector",
  status: "active",
  celExpression: $cel
}' | curl --fail --silent --show-error \
  --request POST \
  https://api.formal.ai/core.v1.DesktopService/CreateDesktopRoutingRule \
  --header "x-api-key: ${FORMAL_API_KEY}" \
  --header "Content-Type: application/json" \
  --data-binary @-

The rule matches known agents only. See Identity headers.Cloud agents such as Claude, ChatGPT and Cursor Cloud Agents don’t run the Endpoint. Point them at this server’s Connector address, https://netlify.<connector-hostname>/mcp. Find it in the Admin Catalog: open Netlify, then copy Connector address on the Configuration tab.

4. Create policies

Tools

The Admin Catalog lists these tools for Netlify:

Tool	Description
`list_sites`	List Netlify sites.
`get_site`	Retrieve site configuration.
`create_site`	Create a site.
`list_deploys`	List site deploys.
`get_deploy`	Retrieve a deploy.
`deploy_site`	Deploy a site.
`get_deploy_logs`	Retrieve deploy logs.
`list_environment_variables`	List environment variables.
`set_environment_variable`	Set an environment variable.

Policies examples

Block a tool

This policy blocks the tools that change data, so agents can only read Netlify.

package formal.v2

import future.keywords.if
import future.keywords.in

write_tools := {
  "create_site",
  "deploy_site",
  "set_environment_variable",
}

request := {
  "action": "block",
  "type": "block_with_custom_message",
  "message": "Writing to Netlify is not allowed.",
} if {
  input.resource.name == "netlify"
  input.mcp.method == "tools/call"
  input.mcp.tool_name in write_tools
}

See MCP resources for the input.mcp fields and Rewrite Action for body rewrites.

5. Check the logs

Open Logs and search for resource.name:netlify. Each Netlify tool call is one request log with the user, the MCP client and the tool. Open a log to see its tool parameters and the policies it triggered. A blocked write shows the block policy and its message.See Logs for search syntax and filters.

Troubleshooting

The agent says Netlify rejected your credentials

The agent relays: netlify rejected your credentials. Link or re-link your netlify account in Formal…Cause: Netlify no longer accepts the linked token, for example after the user revoked access in Netlify.Fix: Link Netlify again from the Employee Catalog.

Laptop traffic doesn't appear in Logs

Cause: The Endpoint isn’t running, or the network rule doesn’t match the client.Fix: Check the Endpoint is connected. The rule above only matches known agents. Other clients, such as a browser, reach Netlify directly unless the rule also matches them. See Network rules.

MCP clients can't connect directly yet

Cause: The Configuration tab lists the reason, most often No Connector is in this server's Space.Fix: Edit the server and choose the Space containing its Connector.

Getting Started

Example Use Cases

AI Governance

Configuring Formal

Integrations

Configuration

0. Prepare your Connector

1. Add Netlify MCP server to your Resources

2. Setup Authentication

Formal’s App (default)

3. Route Endpoint traffic

4. Create policies

Tools

Policies examples

5. Check the logs

Troubleshooting

Next Steps

MCP Gateway

All MCP servers

​0. Prepare your Connector

​1. Add Netlify MCP server to your Resources

​2. Setup Authentication

​Formal’s App (default)

​3. Route Endpoint traffic

​4. Create policies

​Tools

​Policies examples

​5. Check the logs

​Troubleshooting

​Next Steps

MCP Gateway

All MCP servers

0. Prepare your Connector

1. Add Netlify MCP server to your Resources

2. Setup Authentication

Formal’s App (default)

3. Route Endpoint traffic

4. Create policies

Tools

Policies examples

5. Check the logs

Troubleshooting

Next Steps