MCP server · Infrastructure

OfficialSource ValidatedRead-writeISCUpdated August 2026

Netlify MCP

Build, deploy and manage Netlify sites and account resources through Netlify's official hosted MCP server.

Quick verdict

A strong modern-web addition with direct practical value, provided the profile treats production deploys, secret handling and account changes as high-impact operations rather than routine conveniences.

  • MaintainerNetlify (official)
  • Security scopeRead-write
  • Transportsstreamable-http, stdio
  • Install channelremote · https://netlify-mcp.netlify.app/mcp
  • EvidenceSource Validated
  • LicenseISC · Open source

Netlify MCP gives an assistant first-party access to Netlify's API and deployment workflows. It can inspect account context, create and manage projects, trigger builds and deploys, work with forms and extensions, change access controls, and manage environment variables and secrets. Netlify recommends its hosted endpoint for the current capability set and separately publishes the same-family @netlify/mcp npm package (stdio) for constrained environments; this profile uses only the recommended hosted endpoint.

MCP security best practices

Install Netlify MCP

http https://netlify-mcp.netlify.app/mcp

Config entry (mcpServers)
{
  "mcpServers": {
    "netlify-mcp": {
      "url": "https://netlify-mcp.netlify.app/mcp"
    }
  }
}

Netlify's recommended hosted endpoint; the client completes Netlify's interactive authorization flow after connecting. The same netlify/netlify-mcp package also runs locally over stdio (using Netlify CLI login state, or a temporary NETLIFY_PERSONAL_ACCESS_TOKEN for troubleshooting) as a same-family alternative; do not silently substitute npx @netlify/mcp for this endpoint, since the local path adds Node.js, CLI state, local-project and process-execution considerations this profile does not cover.

Credentials

No static secret goes in this config, but this server still requires account authorization. Connecting it starts an interactive sign-in and consent flow against the account it reaches, and whatever that account is allowed to do becomes what the agent can do through this server. Authorize it from an account scoped to the work at hand, and keep your client’s approval prompts on.

Verified configurations

Not run by us yet. This profile is Source Validated: the install channel, config entry, credentials and license were checked against the source and upstream metadata, but no configuration has been installed, discovered and executed in a recorded environment. When one is, it appears here with the eight scope dimensions below.

Best for

Web teams that want an assistant to inspect and manage Netlify projects using a dedicated team or test site and explicit approval before deployments or configuration changes.

Why use it

It packages Netlify's API, deployment expertise and CLI-oriented workflows behind one official server, including an easy hosted connection path that avoids a persistent local runtime.

Tradeoffs

The server can change access controls and secrets, install or uninstall extensions, and deploy code, including to production. Those actions may consume paid usage or replace a live site. The remote and local paths have different trust boundaries, and the documented tool list is broader than a simple deployment-status reader.

Upstream state

repository active. Lifecycle is derived from a committed upstream snapshot at build time, never authored by hand.

Editorial review

Reviewed byOpenSourcesAI EditorialLast updatedAugust 2026SourcesNetlify agent setup and MCP overview; Netlify Codex setup guide; Netlify MCP source repository; Netlify MCP package manifest and ISC license declaration; Official MCP Registry — Netlify search (no entry found; no registryName authored)

Grade B — Source Validated. Re-review is due by 2027-02-18. Config entries, credential names and package status can change upstream; verify against the source repository before granting an agent access.

Sources

Related guides

All MCP servers →