Netlify MCP Server

Netlify MCP Server is the official Model Context Protocol server from the hosting and deployment provider Netlify (netlify.com). It connects AI agents and editors such as Claude Code, Cursor, VS Code, Codex, Windsurf, or Cline to the Netlify API and the Netlify CLI so that an agent can create new projects, build them, deploy them, and manage existing Netlify resources through natural language. The direct starting point is Netlify's documentation at https://docs.netlify.com/build/build-with-ai/agent-setup-guides/agent-setup-overview/, and the source code is public in the repository https://github.com/netlify/netlify-mcp. The npm package is named @netlify/mcp and was at version 1.15.1 under the ISC license when checked on 2026-09-07; the GitHub star count was 60. That number is a point-in-time snapshot of adoption, not a quality or security guarantee.

What the server can do

According to the provider, the server bundles API access, CLI tools, and prepared prompts. With it, an agent can create, link, and deploy projects, trigger Deploy Previews and production deployments, create and change environment variables and secrets, set access controls for stronger project security, install or remove Netlify extensions, manage form submissions, and fetch user and team information. Beyond that, the server ships around a dozen topical "agent skills" that give the model current Netlify knowledge: on Netlify Functions and Edge Functions, on the key-value and object store Netlify Blobs, on the managed Postgres database Netlify DB with Drizzle ORM, on the Image CDN, on forms, on netlify.toml configuration, on CLI and deploy, on framework integrations such as Astro, Vite, Next.js, or TanStack Start, on CDN caching including cache purge, and on the AI Gateway as a proxy for the OpenAI, Anthropic, and Google SDKs.

Setup: hosted or local

There are two paths. The recommended one is the hosted remote server at https://netlify-mcp.netlify.app/mcp; it can be added to compatible clients with npx -y add-mcp https://netlify-mcp.netlify.app/mcp. Alternatively, the server runs locally via npx -y @netlify/mcp or npx -y add-mcp "npx -y @netlify/mcp". The prerequisites are Node.js 22 or newer, a Netlify account, and an MCP-capable client. For Claude Web, Claude Desktop, and ChatGPT you add the server through the respective connector or app and sign in via OAuth. If sign-in fails, Netlify offers a stopgap: a Personal Access Token generated under "User settings > OAuth > New access token" and added temporarily as the environment variable NETLIFY_PERSONAL_ACCESS_TOKEN in the MCP configuration. Netlify explicitly warns not to commit this token to a repository and to remove it again once troubleshooting is done.

How it fits in

Skill Road already lists the Vercel MCP Server; Netlify MCP Server is the counterpart for teams that host on Netlify. The value over plain CLI use is that the agent can query and change deploy status, build logs, configuration, and resources in the same conversation in which it writes code. The DevOps, Coding, and Automation categories fit because the server connects delivery, development work, and repeatable management tasks.

Cost and license

The MCP server itself is open source under the ISC license and free to use. The platform behind it follows the usual Netlify model with a free entry tier, paid plans, and enterprise tiers; the current terms are stated on Netlify's official pricing page. This entry deliberately avoids fixed amounts.

Who the server is for

Netlify MCP Server makes sense for developers and teams that deploy to Netlify often and do not want to leave their AI editor to link a project, review a preview, set environment variables, or investigate a failed build. Anyone who publishes a single static site once is fine with the web interface or the CLI. Before production use, teams should decide which projects an agent may touch, keep access tokens only in environment variables or the client's secure input, and scope the permissions of the account in use as narrowly as possible.

Node.js 22 or newer, a Netlify account, and an MCP-capable client; npx/npm for local operation.

Connect the hosted server with npx -y add-mcp https://netlify-mcp.netlify.app/mcp or register local npx -y @netlify/mcp as the MCP server.

npx -y @netlify/mcp

OAuth sign-in through the client connector (Claude Web/Desktop, ChatGPT); as a stopgap a Personal Access Token in the NETLIFY_PERSONAL_ACCESS_TOKEN environment variable.

The server acts with the permissions of the signed-in Netlify account: projects, deployments, environment variables, secrets, access controls, extensions, and team data.

Prompts and project and deploy parameters go to the Netlify API; responses such as build logs, configurations, and status data return to the MCP client.

A broadly scoped token or account gives an agent write access to production deployments and secrets. Tokens belong only in environment variables or the client's secure input, never in prompts or commits, and should be removed after troubleshooting.