Netlify MCP Server

Netlify MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Manages Netlify sites through the Model Context Protocol.

What you get

A Model Context Protocol (MCP) server for managing Netlify sites. This server enables seamless integration with Netlify's API through MCP, allowing you to create, manage, and deploy sites directly from your MCP-enabled environment.

• 🚀 Create new sites from GitHub repositories
• 📋 List existing Netlify sites with pagination
• 🔍 Get detailed site information
• 🗑️ Delete sites
• 🔐 Secure authentication with Netlify API
• ⚡ Built with TypeScript for type safety

What the assistant can call

Once Netlify is connected, these are the calls the assistant has available:

• createSiteFromGitHub — The createSiteFromGitHub tool exposed by this server
• listSites — The listSites tool exposed by this server
• getSite — The getSite tool exposed by this server
• deleteSite — The deleteSite tool exposed by this server

Configuration and credentials

You will need one environment variable: NETLIFY_ACCESS_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18 or higher - A Netlify account with API access - A GitHub repository for deploying sites

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Netlify's toolset — createSiteFromGitHub, listSites, getSite and 1 more — is a fair guide to whether it matches your workflow. It is maintained by MCERQUA; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Netlify's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the netlify mcp server does with a few real requests.