Netlify MCP Server
Connect Netlify to your AI agents with the Netlify MCP server.
Updated
What is Netlify MCP?
The Netlify MCP server is a Model Context Protocol server that connects Netlify to AI agents and assistants as a set of tools. With it connected, an agent can work with Netlify (web hosting & deploy platform — sites, deploys, builds, env vars, functions) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the Netlify tools become available to the model.
Connect the Netlify MCP server
Connect Netlify MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Netlify MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (OAuth) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Netlify tool to confirm the connection is live.
Connect Netlify MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Netlify
Provide the Netlify MCP server URL or command and complete authentication.
- 3
Test
Reference Netlify from chat to confirm Cursor can reach the tools.
Sample use cases
An agent monitors Netlify deploy status and posts build results to a team Slack channel
Instant deploy visibility without checking the Netlify dashboard.
A scheduled agent checks for failed deploys overnight and creates incident tickets with error logs
Faster incident response for broken production deploys.
An agent triggers a Netlify redeploy after content changes in a headless CMS
Automatic site rebuilds when content is updated, without manual intervention.
An agent audits Netlify environment variables across sites and flags inconsistencies or missing secrets
Reduced configuration drift between staging and production environments.
An agent pulls Netlify analytics data and compiles a weekly site performance report
Consistent traffic and performance reporting without manual data exports.
An agent manages DNS records in Netlify DNS, adding or updating entries when infrastructure changes
Automated DNS management that keeps records in sync with infrastructure.
An agent rolls back a Netlify deploy to the previous version when error rates spike
Automated incident mitigation that restores the last known-good deploy.
Using Netlify MCP with Gamut
On Gamut, the Netlify MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Netlify and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What Netlify operations can agents perform through the MCP server?
Agents can manage sites, trigger and monitor deploys, check build logs, manage environment variables, configure DNS records, and access analytics data through the Netlify MCP server.
Can the Netlify MCP server trigger deploys automatically?
Yes. Agents can trigger new deploys, monitor build progress, and check deploy status. This enables workflows like automatic rebuilds after CMS changes or scheduled deploys.
Does the Netlify MCP server support rollbacks?
Yes. Agents can publish a previous deploy to restore a known-good version of the site, which is useful for automated incident response when error rates spike after a deploy.
Can I manage multiple Netlify sites with one MCP connection?
Yes. The MCP server authenticates at the account level, giving agents access to all sites under the connected Netlify account. Agents can switch between sites in a single workflow.