CLOUD OPERATIONS / Netlify
Netlify MCP
Connect an agent to Netlify project, deployment and environment-variable operations through the hosted server.
“Netlify offers an MCP server, which you can connect to through a connector, plugin, or your agent.”
01 / THE REASONING
Why this made the selection.
- The recommended remote endpoint avoids maintaining a separate local server package.
- OAuth gives compatible clients access to Netlify project and deployment workflows.
- Netlify’s setup guide recommends the remote MCP server for current capabilities, and still documents a local server for environments that require one.
- The publisher README says the hosted server is reached over HTTP and authorizes with OAuth on first use, without a token or a local install, and that its tools cover projects, deploys, and environment variables.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Current Netlify agent setup guide and the publisher’s context-and-tools README MCP section.
- https://docs.netlify.com/build/build-with-ai/agent-setup-guides/agent-setup-overview/
- https://raw.githubusercontent.com/netlify/context-and-tools/main/README.md
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- Netlify recommends the hosted HTTP endpoint; local @netlify/mcp is a separate setup option.
- The publisher documents OAuth and project/deploy/environment tools. Hosted implementation language and redistribution terms are not established by the skills repository.
- The setup guide recommends the remote MCP server so the client gets the current capabilities, and it also documents a local install for environments that require a local server.
- The publisher README says supported plugins connect to the hosted server over HTTP and authorize with OAuth on first use, with no token and no local install.
- Those tools are described as creating and managing projects, deploys, and environment variables, not only the reference skills. Clients that do not bundle the server are told to add it from the docs.
- The current setup overview recommends the hosted server for current capabilities while documenting a local @netlify/mcp alternative.
Not established by this review
- Server launch, authenticated tool calls, and release-to-source parity were not tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
npx -y add-mcp https://netlify-mcp.netlify.app/mcp Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- Run the documented add-mcp command and select your intended client.
- Complete Netlify OAuth when the client first connects.
- Check the active team/project and review changes to deployments or environment variables.
Before you start
- An MCP client supported by the setup flow.
- Node.js/npx for the shown configuration helper and a Netlify account for account operations.
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://docs.netlify.com/build/build-with-ai/agent-setup-guides/agent-setup-overview/
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review
https://raw.githubusercontent.com/netlify/context-and-tools/main/README.md
Supports: summary, whySelected, access, review, limitations, transports