Site and deployment management
Create, manage, and deploy Netlify projects through API/CLI-backed tools.
Documentation ↗MCP server / deployment / source-linked
Netlify MCP
Netlify MCP is the official server that lets code agents use the Netlify API and CLI through natural-language requests. It can create and deploy projects, manage access controls and extensions, inspect teams and forms, and manage environment variables/secrets. The repository documents a local npx configuration and Node.js 22 prerequisite.
Before you choose.
Identify the implementation and the job it supports.
Netlify MCP is the official server that lets code agents use the Netlify API and CLI through natural-language requests. It can create and deploy projects, manage access controls and extensions, inspect teams and forms, and manage environment variables/secrets. The repository documents a local npx configuration and Node.js 22 prerequisite.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- stdio/local package; Netlify also documents a remote endpoint
- Authentication
- Netlify OAuth/CLI context; a PAT can be supplied temporarily for troubleshooting local setup.
Use the official remote quick setup or add @netlify/mcp with npx. Authenticate the client, ensure Node.js 22+, and never commit a PAT if one is used for debugging.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
{"mcpServers":{"netlify":{"command":"npx","args":["-y","@netlify/mcp"]}}}What it actually exposes.
Concrete capabilities with maintainer sources.
Access and extension controls
Modify access controls and install/uninstall Netlify extensions.
Documentation ↗Forms and configuration
Fetch team/user information, manage form submissions, and create/manage environment variables and secrets.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Safe deploy handoff
Suggested evaluation, not an observed test result.
- Connect the target Netlify site with the narrowest available account context.
- Ask the agent to inspect the latest deploy/build output and draft the requested configuration change.
- Review environment-variable or deploy mutations and run a preview before production.
What to inspect: A deploy-ready change plan with explicit site/build evidence and a human approval point. Record the client, selected scope, date, and approval checkpoint so readers can reproduce the decision. Keep the source links beside each claim when publishing the record. Proposed workflow; not tested by clawbot.ai.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
The repository recommends Node.js 22 or newer; older runtimes can break the official setup.
Boundary reference ↗A PAT grants sensitive account access; Netlify says to use it temporarily and remove it after authentication troubleshooting.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A deploy-ready change plan with explicit site/build evidence and a human approval point. Record the client, selected scope, date, and approval checkpoint so readers can reproduce the decision. Keep the source links beside each claim when publishing the record. Proposed workflow; not tested by clawbot.ai.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Vercel MCP | Choose for Vercel deployments, runtime logs, and sandbox tooling. | Vercel is beta and broader; Netlify is direct for Netlify site/build workflows. Documentation ↗ |
| Cloudflare MCP | Choose for edge/DNS/Workers operations rather than site deploy management. | Cloudflare’s API is broad but requires more infrastructure-specific scoping. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
What runtime is required?
Netlify’s repository currently lists Node.js 22 or higher for best results.
Documentation ↗
Should I put a PAT in git?
No. The docs explicitly say not to commit it and to remove it after troubleshooting.
Documentation ↗
Source trail.
Maintainer documentation used in this record.