Netlify MCP Server – Projects and Deployments

Netlify's official MCP server gives AI coding agents structured access to the Netlify API and CLI. Use it to create and manage projects, deploy applications, configure access controls, manage extensions and forms, and work with project environment variables and secrets.

#app-deployment#web-hosting#developer-platform

Overview

Netlify's official MCP server connects compatible code agents to Netlify's API
and CLI. It provides the context and tools an agent needs to create projects,
build applications, and manage deployments through natural-language requests
from an MCP-compatible client.

What the MCP server enables

Netlify documents support for common development and platform-management
workflows. Depending on the authenticated user's team and project permissions,
an AI agent can:

Create, manage, and deploy Netlify projects.
Build applications and manage deployment workflows.
Modify Netlify access controls to protect projects.
Install or uninstall Netlify extensions.
Retrieve Netlify user and team information.
Enable and manage form submissions on projects.
Create environment variables and secrets for projects.
Use Netlify CLI functionality where it is available locally.

When to use it

Use Netlify MCP when an AI coding agent needs current project context or must
perform an approved Netlify operation. Typical workflows include creating a new
project, deploying a web application, configuring project access, enabling
forms, installing an extension, checking team information, or setting
environment variables during application setup.

Connection and authentication

Netlify documents a local stdio configuration using the official
@netlify/mcp npm package. The standard command is
npx -y @netlify/mcp. Node.js 22 or later is recommended, and Netlify also
recommends installing the Netlify CLI globally so the MCP server can use it
directly where possible.

Authentication normally relies on the user's Netlify CLI login session. Users
can verify the session with netlify status or authenticate with
netlify login. Netlify also documents NETLIFY_PERSONAL_ACCESS_TOKEN as a
temporary workaround for persistent login issues.

Key considerations

Netlify recommends adding the MCP server locally at the root of the relevant
project when possible. The server can create deployments, change access
controls, install or remove extensions, and update environment variables, so
require human confirmation for write or production-impacting actions. Keep
personal access tokens out of source control and remove temporary token-based
configuration when it is no longer needed. Use a current Node.js release and
keep the Netlify CLI updated when troubleshooting authentication or tool issues.

Frequently Asked Questions

When should an AI agent use the Netlify MCP server?

Use it when a workflow needs current Netlify project context or approved platform actions, such as creating a project, deploying an application, configuring access controls, managing extensions or forms, retrieving team information, or setting environment variables.

What does the Netlify MCP server add to an AI agent's capabilities?

It gives the agent structured access to Netlify API and CLI functionality, allowing it to build, deploy, and manage current Netlify projects instead of relying only on static model knowledge or manually copied dashboard data.

What can an AI agent access or manage through Netlify MCP?

Depending on account permissions, the agent can work with projects, deployments, access controls, extensions, forms, users, teams, environment variables, secrets, and other supported Netlify API or CLI operations.

How is authentication configured for the Netlify MCP server?

The standard setup uses the authenticated Netlify CLI session. Users can sign in with `netlify login` and verify authentication with `netlify status`. Netlify also documents NETLIFY_PERSONAL_ACCESS_TOKEN as a temporary workaround, but the token must be stored securely and never committed to source control.

Which transport should be used for the Netlify MCP server?

Use stdio with the official @netlify/mcp npm package. Netlify's documented client configurations launch the server locally with npx, and no official hosted Streamable HTTP or SSE endpoint is included in this YAML.