Netlify MCP server
Last verified: 2026-09
Sites and deploys on Netlify.
Community Cloud & infra Needs a secret Claude Desktop, Cursor, Windsurf, Claude Code
What it does
Official Netlify MCP. Sites, deploys, and project ops through NETLIFY_AUTH_TOKEN. Check the connected tool list — the README is setup-heavy.
It sits in Cloud & infra: Most of these are admin APIs.
Good for
- List sites the PAT can see.
- Inspect a deploy without opening the UI.
- Keep delete-site off production.
- Fix Node version mismatches using their troubleshooting before you blame MCP.
Tools
- sites / deploys / project tools — List and manage sites the token can see. Confirm names after connect.
Config (Claude Desktop / Cursor / Windsurf)
Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets.
Windows paths look like C:\\Users\\you\\project, not /path/to.
Host-side steps →
Claude Desktop
| OS | Config file |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json
(usually C:\Users\<you>\AppData\Roaming\Claude\) |
| Linux | ~/.config/Claude/claude_desktop_config.json |
Cursor
| Scope | macOS / Linux | Windows |
|---|---|---|
| This project | .cursor/mcp.json in the repo root | |
| This user | ~/.cursor/mcp.json |
%USERPROFILE%\.cursor\mcp.json |
Windsurf
| OS | Config file |
|---|---|
| macOS / Linux | ~/.codeium/windsurf/mcp_config.json |
| Windows | %USERPROFILE%\.codeium\windsurf\mcp_config.json |
{
"mcpServers": {
"netlify": {
"command": "npx",
"args": [
"-y",
"@netlify/mcp"
],
"env": {
"NETLIFY_AUTH_TOKEN": "..."
}
}
}
}
Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.
One-liner: npx -y @netlify/mcp
Secrets it wants: NETLIFY_AUTH_TOKEN
How to get started
- Create a Netlify PAT. Scope it to one team.
- Ask it to list sites. Do not let it delete a production site.
- Node version mismatches are a common install failure — see their troubleshooting.
Access risk
Auth token can deploy and tear down sites. Env vars on Netlify are in scope for some APIs.
When to skip it
Skip it for Vercel or Cloudflare.
Instead: Vercel, Cloudflare, GitHub.
Vs alternatives
| Server | Official? | Needs a secret? | Best for |
|---|---|---|---|
| Netlify | No | Yes | Sites and deploys on Netlify. |
| Vercel | No | Yes | Projects and deployments on Vercel. |
| Cloudflare | No | Yes | Workers, KV, R2, and DNS via Cloudflare. |
| GitHub | Yes | Yes | Repos, issues, PRs, and file contents on GitHub. |
More in Cloud & infra
FAQ
Official Netlify?
Yes — @netlify/mcp. README is setup-heavy; list tools after connect.
Which token?
NETLIFY_AUTH_TOKEN scoped to one team. Env vars on Netlify are in scope for some APIs.
Netlify or Cloudflare Pages?
Match the host.
Can it ship a deploy?
If the tools include deploy/publish, yes. Same as handing someone the Netlify UI.