# Netlify — MCP Server

> Let an agent deploy, configure and debug a Netlify site.

**Source:** https://mcpplaygroundonline.com/mcp-servers/netlify  
**Transport:** stdio  
**Requires auth:** Yes

---

## What it does

Most deploy integrations stop at "push and hope". This one gives an agent the feedback it needs to actually finish the job: after a deploy it can read the build logs, see why the build failed, fix the configuration and redeploy. Around that core it covers the platform surface — creating and listing sites, managing environment variables per context, installing and configuring extensions such as Auth0 or a database provider with preconfigured defaults, reading form submissions, and handling team and user management. Because it runs over stdio through the Netlify CLI package, it authenticates with whatever Netlify session you already have on the machine, or with a personal access token when you want to scope it explicitly. It works with any MCP-capable coding agent — Claude Code, Cursor, Windsurf, VS Code Copilot.

## Tools exposed

- deploy site — deploy a directory to a Netlify site, with branch and context awareness
- deploy logs — read build output to diagnose a failed deploy and retry
- site management — create, list and configure sites and their build settings
- environment variables — read and set variables per deploy context
- extensions — install and configure extensions such as auth and database providers
- forms — list forms and read submissions
- team and user management — account-level operations

## Example queries you can run

- "Deploy this project to a new Netlify site and give me the URL."
- "The last deploy failed — read the build log and tell me what broke."
- "Set these environment variables on the production context only."
- "Which of my sites have not been deployed in the last 90 days?"

## Details

- **Recommended model:** anthropic/claude-sonnet-4.5 — The valuable loop here is deploy, read the failing build log, fix, redeploy. Sonnet 4.5 diagnoses build errors accurately enough to make that loop terminate.
- **Transport:** stdio
- **Authentication:** Required — Your existing Netlify CLI login, or a personal access token in NETLIFY_PERSONAL_ACCESS_TOKEN when you want to scope it explicitly.
- **Official source:** [netlify/netlify-mcp — official repository](https://github.com/netlify/netlify-mcp)

## Connecting to Netlify

### Environment variables

- `NETLIFY_PERSONAL_ACCESS_TOKEN` — Personal access token from Netlify user settings. Optional if you are already logged in with the Netlify CLI.

### Client configuration

**npx (recommended)**

Uses the Netlify session already on the machine — no token needed if you have run netlify login.

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

**With an explicit access token**

Use this in CI, or when you want the agent scoped to a specific account rather than your CLI session.

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

## Frequently asked questions

### What is the Netlify MCP server?

It is Netlify’s official MCP server, published as @netlify/mcp. It lets an AI coding agent create and deploy sites, read deploy logs, manage environment variables, install extensions and handle forms and team settings.

### Can an agent deploy straight to production?

It can, which is exactly why you should decide deliberately. Pointing the agent at a branch deploy or a preview context gives you the same feedback loop without a production change, and is the sane default while you are learning how it behaves.

### How does it authenticate?

It uses your existing Netlify CLI session if you have one, so netlify login is often the whole setup. Setting NETLIFY_PERSONAL_ACCESS_TOKEN instead is the better route for CI or when you want the agent bound to one specific account.

### Why does reading deploy logs matter so much?

Because it is what turns a one-shot deploy into a loop that converges. Without log access the agent deploys, the build fails, and it has nothing to act on. With it, the agent reads the actual error, fixes the config and redeploys — usually in one or two rounds.

### Does it work with agents other than Claude?

Yes. It is a standard stdio MCP server and works with Cursor, Windsurf, VS Code Copilot, Claude Code and anything else that speaks MCP. You can also test it against any model in MCP Agent Studio before committing to one.

---

_Test this server across 40+ models on MCP Playground: https://mcpplaygroundonline.com/mcp-servers/netlify — free, no install._