Netlify MCP Server: Tools, Setup and Security

The Netlify MCP Server lets AI agents use the Netlify API and CLI to create, build, deploy and manage Netlify projects in plain language. Netlify publishes it, with a remote version it recommends and a local npm package.

Checked against: Netlify MCP Server docs on 28 October 2026. eSEOspace did not install or test this server.

At a glance

What it can do

The netlify-mcp README describes the server as "a bridge, providing API access, CLI tools, prompts, and more for your agents." It lists these use cases:

• Create, manage and deploy Netlify projects.
• Modify access controls for project security.
• Install or uninstall Netlify extensions.
• Fetch user and team information.
• Enable and manage form submissions.
• Create and manage environment variables and secrets.

The README ends that list with "and more." Netlify's docs page does not list individual tool names, so this profile does not name any. Your client will show the live tool list after you connect.

For agencies and marketing teams, the common uses are clear. An agent can spin up a preview site, push a deploy, or check which form submissions arrived. That is also why the access controls and secrets tools deserve care.

How to connect it

Remote (recommended). Netlify's docs give one command that detects your agents and configures them:

npx -y add-mcp https://netlify-mcp.netlify.app/mcp

The docs' one-click installers use this config:

{
  "url": "https://netlify-mcp.netlify.app/mcp"
}

Netlify links separate guides for Claude Code, Codex, Claude Web, Claude Desktop, ChatGPT, Grok, Antigravity and Antigravity CLI.

Local. Netlify says some developers must use local servers. Its command:

npx -y add-mcp "npx -y @netlify/mcp"

Or add this to your client's MCP config file, as the README shows:

{
  "mcpServers": {
    "netlify": {
      "command": "npx",
      "args": [
        "-y",
        "@netlify/mcp"
      ]
    }
  }
}

Prerequisites for local use are Node.js 22 or higher (per the README; Netlify's Claude Code guide says Node 24 or higher), a Netlify account and an MCP client. Netlify also suggests installing the Netlify CLI globally with npm install -g netlify-cli.

Security notes

• Secrets are in scope. The server can create and manage environment variables and secrets. Anything an agent reads can end up in its context. See secret leakage in MCP.
• Access controls are in scope. An agent can change project access controls, so review those actions before you approve them.
• Tokens as a last resort. For authentication problems, the README shows adding a Personal Access Token as NETLIFY_PERSONAL_ACCESS_TOKEN. It says in bold: "Do not commit your PAT to your repository!" Remove it once the issue is fixed.
• Check the source. Use the URL and package name from Netlify's own docs. Lookalike packages are a known MCP supply chain risk.

Netlify's MCP pages do not describe a read-only mode or per-tool permissions. Keep approvals on in your client, and see the MCP security hub for general controls.

Alternatives

• Vercel MCP for projects hosted on Vercel.
• Cloudflare MCP Server for Cloudflare Pages, Workers and DNS.
• Render MCP Server for static sites and web services on Render.

Next step

If your agency deploys client sites on Netlify, test the remote server on a sandbox team first. Our MCP servers for developers list compares the hosting servers, and the server directory has more profiles.

Frequently asked questions