Netlify

You can run a Netlify MCP Server locally to access Netlify CLI features through a structured, non-interactive interface. This server lets you perform deployments, manage sites, work with environment variables, access blob storage, run functions, and more, all via MCP-compatible commands and data streams. It centralizes Netlify operations for automated workflows and multi-tool integrations.

How to use

To use the Netlify MCP Server, configure an MCP client to connect to the local server, then call the supported tools to manage Netlify sites, deployments, and related resources. You will authenticate with a Personal Access Token (PAT) and pass it to the server through an environment variable. The server exposes a rich set of commands for site management, deployments, environments, functions, blobs, recipes, analytics, forms, and API access, all designed for programmatic use in automation pipelines.

How to install

Prerequisites: Node.js installed on your machine, and a command-line environment you can run commands from. You will also need a Netlify Personal Access Token (PAT) to authenticate non-interactively.

Step 1: Install the MCP server client (example uses the Smithery CLI install flow to provision Claude Desktop with the Netlify MCP Server). Run just this command in your terminal:

npx -y @smithery/cli install @DynamicEndpoints/Netlify-MCP-Server --client claude
```} ,{

Step 2: Create an MCP settings configuration to run the server locally. Use the following JSON snippet exactly as shown to define the MCP server connection. This uses a local stdio server that starts the MCP runtime with Node.

{
  "mcpServers": {
    "netlify": {
      "command": "node",
      "args": ["C:\\path\\to\\Netlify-MCP-Server\\build\\index.js"],
      "env": {
        "NETLIFY_AUTH_TOKEN": "YOUR_NETLIFY_PAT_HERE"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}
```} ,{

Step 3: Ensure Netlify CLI authentication is provided via a Personal Access Token. Prepare the PAT and keep it secure. You will set NETLIFY_AUTH_TOKEN in the MCP server configuration as shown above.

Additional setup and constraints

Netlify MCP Server is designed for non-interactive use. Do not rely on browser-based login flows. The server expects a PAT and passes site context through environment variables (for example, NETLIFY_SITE_ID when required). Some interactive features or browser-dependent steps may not be fully supported in MCP mode.

If you run into issues, verify that the server process is running, the PAT is valid, and the required environment variables are present in the server configuration. Check your MCP client’s logs for error details and confirm that the target Netlify resources exist and you have access rights.

Configuration and security notes

Configuration is provided as a JSON block that you place in your MCP client’s settings. It defines the Netlify server as a local stdio process and passes the authentication token via NETLIFY_AUTH_TOKEN.

Security best practices: store the PAT securely, rotate tokens regularly, and minimize token scope to the needed permissions. Do not expose the token in logs or shared configurations. When possible, use separate tokens for different automation pipelines or environments.

Troubleshooting tips

If commands fail to execute, confirm the following: the MCP server process is running, the path to build/index.js is correct, and NETLIFY_AUTH_TOKEN is set correctly in the server’s environment. Review any error messages to identify missing permissions, invalid site references, or network issues reaching Netlify services.

Available tools

deploy-site

Deploy a site directory to Netlify (production or preview)

list-sites

List all Netlify sites linked to your account

trigger-build

Trigger a new build and deploy for a site

build-site

Build a Netlify site locally with context options

link-site

Link the current project directory to a Netlify site

unlink-site

Unlink the current project directory from the linked Netlify site

get-status

Show the Netlify status for the linked site/directory

init-site

Initialize a new site in the current directory

open-site

Open site in the browser or admin panel

set-env-vars

Set environment variables for a site

get-env-var

Get a specific environment variable value

unset-env-var

Unset an environment variable

import-env

Import environment variables from a file

clone-env-vars

Clone environment variables between sites

list-deploys

List deploys for a site

get-deploy-info

Get information about a specific deploy

cancel-deploy

Cancel a running deploy

restore-deploy

Restore a previous deploy

watch-deploy

Watch deployment progress in real-time

list-functions

List all functions for a site

get-logs

Get function logs for a site

build-function

Build a serverless function

invoke-function-advanced

Invoke function with advanced options

get-blob

Get a blob from Netlify Blobs storage

set-blob

Set/store a blob in Netlify Blobs storage

delete-blob

Delete a blob from storage

list-blobs

List all blobs in a store

start-dev-server

Start Netlify dev server locally

serve-built-site

Serve a built site locally

list-recipes

List available Netlify recipes

run-recipe

Run a specific Netlify recipe

call-netlify-api

Make direct Netlify API calls

list-api-methods

List available API methods

get-form-submissions

Get form submissions for a site

manage-form

Manage site forms and submissions

get-analytics

Get site analytics data

stream-logs

Stream real-time logs from functions

enable-branch-deploy

Enable branch deploys for a specific branch

disable-branch-deploy

Disable branch deploys for a specific branch

switch-account

Switch between Netlify accounts