What it is
The Netlify MCP Server lets coding agents create and deploy Netlify projects, manage visitor access controls, install extensions, handle form submissions, read observability data and set environment variables and secrets. It combines Netlify API access with Netlify CLI tools.
Netlify recommends its remote server at https://netlify-mcp.netlify.app/mcp, installed with npx -y add-mcp or through the Claude connector and ChatGPT app. A local version runs with npx -y @netlify/mcp and needs Node.js 22 or later; if sign-in fails, the README suggests temporarily adding a personal access token.
Releases are weekly: 1.20.0 shipped on 20 October 2026, after 1.19.0 added observability tools and fixed OAuth state signing. The repository has no licence file, although the npm package declares ISC, and the server has no entry in the official MCP registry.
Install
https://netlify-mcp.netlify.app/mcpOur review
Netlify's server does the deploy loop well, and its real cost sits in Netlify's credit meter rather than in the server. Each production deploy costs 15 credits, so the Free plan's 300 credits cover 20 of them. An agent that redeploys after every small fix can use up a month's allowance in an afternoon.
The tool design is better than the documentation suggests. Rather than dozens of tools, the server groups operations into six domains (user, team, project, deploy, extensions and observability) and registers a read-only and a write tool for each, with an operation selector. That keeps the tool list short and lets a client auto-approve reads. Since 1.18.0, OpenAI clients get one tool per operation with its own annotations, and project renames are marked destructive.
The documentation remains thin. The docs page covers installation and agent skills but has no tool list and no security guidance; the README describes use cases in a few bullets. You learn the real surface by reading src/tools, where the authors' own checklist still marks rollbacks, domains and build settings as not done. The changelog shows security work, such as signing the OAuth authorize state in 1.19.0 (SEC-790), without a published advisory.
Write reach is broad: environment variables and secrets, visitor access controls, extension installs and production deploys across every team the account belongs to. The personal-access-token fallback grants the same reach and lives in a config file, which is why the README shouts not to commit it. The missing licence file matters less to users than to anyone who wants to fork or audit the code.
Where it earns its place
A freelance developer shipping client marketing sites from Claude Code
Create a project, set env vars and deploy without opening the dashboard
Connect the remote server, sign in, and ask the agent to create the project, add environment variables and deploy. Personal at $9 a month includes 1,000 credits, about 66 production deploys if bandwidth is light, so batch fixes before deploying.
A front-end lead on a six-person team on Netlify Pro
Diagnose a failed deploy from the editor
Auto-approve the read tools, including get-deploy and the observability domain added in 1.19.0, and keep the deploy and env-var write tools behind approval. Pro is $20 a month for 3,000 credits, with 1,500-credit packs at $10.
A platform manager at an agency hosting 40 client sites
Let agents manage some sites without exposing every client's secrets
The server acts across every team the signed-in user belongs to, including team env vars, so give agents a Netlify user that belongs only to the teams they need. SSO and SCIM are Enterprise-only, on custom pricing.
Before you commit
- Setup
- Run npx -y add-mcp https://netlify-mcp.netlify.app/mcp, or use the Claude connector, the ChatGPT app or one-click installs for Cursor, LM Studio and VS Code, then sign in to Netlify in the browser. Locally, npx -y @netlify/mcp on Node.js 22+, with a personal access token as a temporary fallback.
- Integrations
- Operations across six domains, registered as one read-only and one write tool per domain, or individually in verbose mode. They include deploy-site, get-deploy, manage-project-env-vars, manage-form-submissions, update-visitor-access-controls and change-extension-installation.
- Data and privacy
- The server acts as your Netlify user: it can read and change env vars and secrets, form submissions, access controls and production deploys across your teams. The remote server is run by Netlify; 1.19.0 fixed OAuth state signing (SEC-790) with no separate advisory.
- Cost at scale
- The server is free; actions spend credits. Free has 300, Personal $9 for 1,000, Pro $20 for 3,000; a production deploy costs 15 credits, bandwidth 20 per GB, compute 10 per GB-hour and web requests 2 per 10,000. Pro credit packs are 1,500 for $10.
- Limits
- No published tool list or rate limits. Rollback, domain and build-settings operations are unchecked in the source's own to-do list, and the repository has no licence file.
What's good
- Hosted server recommended, with a local npx fallback
- Read and write tools split per domain, so reads can be auto-approved
- Covers deploys, env vars, forms, access controls and extensions
- Weekly releases, with tool annotations since 1.18.0
What's not
- Each production deploy costs 15 credits
- No published tool list or security guidance
- No licence file; only package.json declares ISC
- No rollback or domain operations yet
Best for
Netlify users who want their coding agent to deploy and manage sites directly.
Alternatives
Netlify MCP Server: common questions
- Is Netlify MCP Server worth it?
- Handles Netlify's deploy loop competently, though an eager agent can spend a month of credits before anyone checks the bill. We rate it 3.9 out of 5.
- How much does Netlify MCP Server cost?
- Server is free; actions spend Netlify credits. Free plan 300 credits a month, Personal $9/month (1,000), Pro $20/month (3,000); a production deploy costs 15 credits.
- What are the downsides of Netlify MCP Server?
- Each production deploy costs 15 credits; no published tool list or security guidance; no licence file; only package.json declares ISC; no rollback or domain operations yet.
- Who is Netlify MCP Server best for?
- Netlify users who want their coding agent to deploy and manage sites directly.
- How much does Netlify MCP Server cost for a team or in production?
- The server is free; actions spend credits. Free has 300, Personal $9 for 1,000, Pro $20 for 3,000; a production deploy costs 15 credits, bandwidth 20 per GB, compute 10 per GB-hour and web requests 2 per 10,000. Pro credit packs are 1,500 for $10.
- Is Netlify MCP Server safe for company data?
- The server acts as your Netlify user: it can read and change env vars and secrets, form submissions, access controls and production deploys across your teams. The remote server is run by Netlify; 1.19.0 fixed OAuth state signing (SEC-790) with no separate advisory.
- What are the best Netlify MCP Server alternatives?
- The closest alternatives we have reviewed are Vercel MCP and Cloudflare MCP Server.
Answers checked Oct 23, 2026.