A Netlify MCP that can roll production back in one call
Connect one Personal Access Token and Netlify sites, deploys, builds, build hooks, environment variables, DNS, and forms become workflow steps for visual automations and AI agents. The headline is rollback: restore any specific past deploy as the live site, or flip back to the previous one in a single call with no deploy id needed.
What the Netlify MCP connector does
The Netlify connector for Mattering Automations is 39 nodes across the API: sites (list, inspect, update, delete), the deploy lifecycle (list, inspect, cancel, lock and unlock auto-publishing, restore a specific past deploy, roll back to the previous one), builds and the team's build minutes usage, build hooks (create, trigger, delete), environment variables with per-context values, DNS zones and records, and Netlify Forms submissions.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer which deploy is live, why the last build failed, and how many build minutes the team has used this billing period, without anyone opening the Netlify dashboard.
Because Mattering is a work platform rather than middleware, hosting work lands somewhere useful by default: a scheduled deploy sweep can open a task in Mattering Productivity when a production deploy fails, log the incident to a Mattering database, and hold a gated rollback step ready, all on one canvas next to the rest of the work.
The connector is honest about cost and secrecy. Netlify: Start Build and Netlify: Trigger Build Hook start real CI builds that consume the account's build minutes, and past the plan's included allowance Netlify charges for extra minutes, so Netlify: Get Account Build Status sits beside them to check the queue and the minutes counter first. Reading environment variables copies their unencrypted values into automation execution records, and the read nodes say so plainly; Netlify's write-only secret variables are the real fix. Five destructive nodes (the site, build hook, environment variable, DNS record, and form submission deletes) are flagged so they can be gated or left out entirely.
One connection, three surfaces
- Visual automations. Drag Netlify nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Netlify node, ready to drop on the canvas
39 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 21
Netlify: Get Account Build Status
Show the team's current build queue (active and enqueued builds) and build-minutes usage for the billing period. Check this before start-build automations to avoid burning through the plan's included minutes.
Netlify: Get Build
Fetch one build by id: done flag, error message, and the deploy_id it produced. Poll after Netlify: Start Build to follow progress.
Netlify: Get Build Hook
Fetch one build hook by id: title, target branch, and the trigger URL.
Netlify: Get Current User
Return the account of the user the access token belongs to: name, email, site count, last login. Takes no parameters, so it doubles as the credential health check for the connector.
Netlify: Get DNS Record
Fetch one DNS record by id.
Netlify: Get DNS Zone
Fetch one DNS zone: domain, name servers, supported record types, and the account and site it belongs to.
Netlify: Get Deploy
Fetch one deploy by id: state (new, building, ready, error), branch, commit, error_message and URLs. Poll this after starting a build to know when the deploy goes live or fails.
Netlify: Get Environment Variable
Fetch one environment variable by key, with its values per deploy context. WARNING: the response contains each variable's UNENCRYPTED value, and node outputs are stored in automation execution records, so running this copies the values into execution history. Variables created with is_secret true come back with values omitted; mark sensitive variables as secret in Netlify if they must stay unreadable.
Netlify: Get Form Submission
Fetch one form submission by id, with every submitted field under data.
Netlify: Get Site
Fetch one site: state, URLs, custom domain, build settings, and the currently published deploy (its id is what rollback and restore work against).
Netlify: List Accounts
List the teams (accounts) the token can access, with plan and usage capabilities. The account id or slug returned here is what the environment variable and build status nodes need.
Netlify: List Build Hooks
List a site's build hooks: incoming URLs that trigger a build of a set branch when POSTed to. Each hook's url and id feed the trigger and delete nodes.
Netlify: List DNS Records
List every DNS record in a zone: type, hostname, value, TTL. Records with managed true are Netlify-managed (created automatically for its own services).
Netlify: List DNS Zones
List the DNS zones (domains on Netlify DNS) the token can access, with name servers and linked sites. Zone ids feed the record nodes.
Netlify: List Environment Variables
List environment variables for a team, or for one site via site_id, with per-context values. WARNING: the response contains each variable's UNENCRYPTED value, and node outputs are stored in automation execution records, so running this copies the values into execution history. Variables created with is_secret true come back with values omitted; mark sensitive variables as secret in Netlify if they must stay unreadable.
Netlify: List Form Submissions
List verified submissions of ONE form, newest first, with the submitted field data under data. The new-form-submission automation usually starts here.
Netlify: List Site Builds
List a site's builds, newest first, each linking to the deploy it produced (deploy_id) with done and error status.
Netlify: List Site Deploys
List a site's deploys, newest first, with state, branch, commit and URLs. Filter to production deploys, deploy previews, a branch, or a state; latest-published narrows to the deploy currently live. The ids here feed the restore, cancel and lock nodes.
Netlify: List Site Form Submissions
List verified form submissions across ALL forms on a site, newest first, with the submitted field data. Submissions can contain visitors' personal data; handle downstream accordingly.
Netlify: List Site Forms
List the Netlify Forms detected on a site, with field definitions and submission counts. Form ids feed the submissions nodes.
Netlify: List Sites
List the sites the token can access, with URLs, custom domains, build settings and the currently published deploy. Filter by exact name or by ownership, and page with page/per_page.
Action nodes 18
Netlify: Cancel Deploy
Cancel a deploy that is still processing. The deploy ends in an error state and the currently published version stays live; recover by starting a new build. Only in-progress deploys can be cancelled.
Netlify: Create Build Hook
Create a build hook for the site: the response's url is an unauthenticated endpoint that starts a build of the chosen branch whenever it receives a POST. Treat that URL as a secret; anyone holding it can trigger builds (which consume build minutes).
Netlify: Create DNS Record
Create a DNS record in a zone. CAUTION: this changes LIVE DNS for a real domain as soon as it propagates; a wrong record can misroute mail (MX) or traffic. Reversible by deleting the record, but propagation and caching mean mistakes can linger up to the TTL.
Netlify: Create Environment Variables
Create one or more environment variables on the team, or on one site via site_id. Each variable carries per-context values and optional scopes. For anything sensitive set is_secret true: secret values are write-only afterwards (unreadable via UI, API and CLI), which is Netlify's own mechanism for keeping credentials out of places like automation execution records.
Netlify: Delete Build Hook
DESTRUCTIVE: delete a build hook. Its URL stops working immediately and cannot be recreated with the same id, so every external service pointed at it silently stops triggering builds. Returns 204 with an empty body.
Netlify: Delete DNS Record
DESTRUCTIVE: delete a DNS record from LIVE DNS. Deleting the wrong record can take a site or its email offline until the record is recreated and propagates. Read the record first (Netlify: Get DNS Record) so it can be recreated if needed. Returns 204 with an empty body.
Netlify: Delete Environment Variable
DESTRUCTIVE: delete an environment variable and every one of its context values (team-wide, or from one site via site_id). Secret values cannot be read back before deleting, so there is no way to restore them afterwards. The next build runs without the variable. Returns 204 with an empty body.
Netlify: Delete Form Submission
DESTRUCTIVE: permanently delete a form submission and its data; there is no undo. Useful for spam cleanup and data-removal requests. Returns 204 with an empty body.
Netlify: Delete Site
DESTRUCTIVE: permanently delete a real site, its deploy history, forms and settings. The site stops serving immediately and there is no undo via the API. Returns 204 with an empty body on success.
Netlify: Lock Deploy (Stop Auto-Publishing)
Lock the site to this published deploy: new builds still run but stop being auto-published, freezing production at the locked version (a change freeze in one call). Undo with Netlify: Unlock Deploy.
Netlify: Restore Deploy (Rollback to Deploy)
Publish a specific past deploy again, making it the live production version of the site: the roll-back-to-known-good workflow. Takes effect immediately on the live site; reversible by restoring another deploy. Pick the deploy id from Netlify: List Site Deploys.
Netlify: Rollback Site to Previous Deploy
Roll the site back to the deploy that was published before the current one, in one call with no deploy id needed. Takes effect immediately on the live site. Returns 204 with an empty body; follow with Netlify: Get Site to see the newly published deploy. For rolling back to a SPECIFIC older deploy, use Netlify: Restore Deploy instead.
Netlify: Set Environment Variable Value
Set the value of an EXISTING environment variable for one deploy context, leaving its other context values alone: the day-to-day update node. New values apply from the next build or function reload, not retroactively to the running deploy.
Netlify: Start Build
Trigger a new build of the site from its linked repository, producing a fresh deploy. No branch means a production build; a non-main branch produces a branch deploy. This is also the retry-a-failed-deploy move (optionally with clear_cache). This starts a real CI build that consumes the account's build minutes; beyond the plan's included allowance Netlify charges for extra minutes. Netlify also rate-limits deploy-producing calls to 3 per minute and 100 per day.
Netlify: Trigger Build Hook
Fire a build hook, starting a build exactly as an external service POSTing the hook URL would (note the hook endpoint itself needs no auth; the unguessable id is the credential). Optionally override the branch and deploy title or clear the cache. This starts a real CI build that consumes the account's build minutes; beyond the plan's included allowance Netlify charges for extra minutes. Netlify also rate-limits deploy-producing calls to 3 per minute and 100 per day.
Netlify: Unlock Deploy (Resume Auto-Publishing)
Release a deploy lock so new production builds auto-publish again. Pass the id of the locked deploy.
Netlify: Update Environment Variable (Replace)
Replace an environment variable wholesale: rename it, change its scopes, or REPLACE ITS ENTIRE VALUES LIST (context values missing from the new list are dropped). For changing one context's value, prefer Netlify: Set Environment Variable Value. Setting is_secret true makes the values write-only from then on.
Netlify: Update Site
Update a site's settings: rename it (changes its netlify.app URL), point its custom domain, set or clear password protection, toggle HTTPS forcing, or patch any other documented site attribute through the body field. Changes to name and custom_domain affect the LIVE site's URLs immediately.
Connecting Netlify takes one credential
Netlify issues Personal Access Tokens from User settings under Applications. A token is sent as a bearer credential on every request and needs no OAuth flow for automating your own team. Tokens carry the expiration date you choose at creation, and a Netlify password reset revokes every existing token at once.
In Netlify, open User settings, go to Applications, and create a Personal Access Token, choosing an expiration date and noting it somewhere the team will see.
In Mattering Automations, open Connectors, click Add Connector, choose Netlify, and create a credential with that token.
Click Test Connection. Mattering calls Netlify's user endpoint, a tiny read that is valid for every token, and confirms the token authenticates.
All 39 Netlify nodes appear in the canvas palette. Run Netlify: List Sites first: nearly every other node wants a site id it returns.
Common uses for the Netlify MCP
Rollback as a first-class workflow step
Netlify: Restore Deploy (Rollback to Deploy) publishes a specific past deploy as the live site, the roll-back-to-known-good move, with the deploy id chosen from Netlify: List Site Deploys. Netlify: Rollback Site to Previous Deploy is the one-call version: no deploy id, just flip back to whatever was published before. Both take effect immediately on the live site, and both are reversible by restoring another deploy.
Deploy watching without the dashboard
Run Netlify: List Site Deploys on a schedule, filter to production deploys, and route state changes into tasks, records, or messages: a deploy that lands in error can open a ticket with its error_message, branch, and commit attached, and Netlify: Get Deploy follows a single deploy from building to ready or error.
Builds with the cost in plain sight
Netlify: Start Build triggers a fresh build from the linked repository, and it is also the retry move: Netlify's API has no retry endpoint, so retrying a failed deploy means starting a new build, optionally with a cleared cache. Builds consume real build minutes, and Netlify rate-limits deploy-producing calls to 3 per minute and 100 per day, so Netlify: Get Account Build Status is there to check the build queue and the minutes counter before anything triggers.
A change freeze in one call
Netlify: Lock Deploy (Stop Auto-Publishing) pins production at the locked deploy: new builds still run, but they stop being auto-published, which is a change freeze without touching the repository. Netlify: Unlock Deploy (Resume Auto-Publishing) releases it when the freeze is over.
Environment variables, handled honestly
Netlify: Create Environment Variables, Netlify: Set Environment Variable Value, and Netlify: Update Environment Variable (Replace) manage per-context values, and the read nodes warn plainly: responses contain unencrypted values, and node outputs are stored in automation execution records. For anything sensitive, create the variable with is_secret true, which makes its values write-only afterwards, Netlify's own mechanism for keeping credentials out of places like execution history.
Forms and DNS from the same canvas
Netlify: List Site Forms, Netlify: List Form Submissions, and Netlify: Get Form Submission turn form entries into workflow input, with Netlify: Delete Form Submission for spam cleanup and data-removal requests. Netlify: Create DNS Record and Netlify: Delete DNS Record manage records inside existing zones, with the plain caution that this is live DNS for a real domain and mistakes can linger up to the TTL.
Example: Failed production deploys open a task, with rollback one gated step away
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a schedule runs the check every few minutes.
Netlify: List Site Deploys pulls the newest production deploys with state, branch, commit, and error_message.
A condition checks a Mattering database of already-seen deploy ids and passes only new deploys whose state is error.
A task opens in Mattering Productivity with the branch, commit, and error message attached, so a person sees the failure where the rest of the work lives.
Netlify: Get Site adds the currently published deploy to the task, confirming what is still live while the failure is investigated.
A separately gated Netlify: Rollback Site to Previous Deploy waits behind an approval step for the case where a bad deploy actually went live; to return to a chosen known-good version instead, Netlify: Restore Deploy (Rollback to Deploy) takes a specific deploy id.
Netlify MCP questions, answered
What Netlify operations are supported?
39 nodes: sites (list, get, update, delete), deploys (list, get, cancel, lock and unlock auto-publishing, restore a specific deploy, roll back to the previous one), builds (list, get, start) plus the team's build queue and minutes usage, build hooks (list, get, create, trigger, delete), environment variables (list, get, create, set one context's value, replace, delete), DNS zones and records, and Netlify Forms (forms, submissions per form and per site, get and delete a submission). Deliberately not shipped: the file-digest deploy upload flow (deploys are triggered through builds and build hooks instead), site creation, outbound notification hooks, DNS zone lifecycle, and Netlify's OAuth app flow, since Personal Access Tokens cover automating your own team.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
How does rolling back a site work?
Two ways. Netlify: Restore Deploy (Rollback to Deploy) publishes a specific past deploy again, making it the live production version; pick the deploy id from Netlify: List Site Deploys. Netlify: Rollback Site to Previous Deploy needs no id at all and flips the site back to the deploy that was published before the current one; it returns an empty 204, so follow it with Netlify: Get Site to see what is now live. Both take effect immediately and both are reversible by restoring another deploy.
Is it safe to read environment variables through automations?
Read the warning first. Netlify's API returns environment variable values unencrypted, and node outputs are stored in automation execution records, so running Netlify: List Environment Variables or Netlify: Get Environment Variable copies plaintext values into execution history. The connector does not silently redact them, because that would break legitimate reads and fake a safety property the platform does not have. The real fix is Netlify's own: variables created with is_secret true are write-only afterwards (unreadable via UI, API, and CLI, and returned with values omitted), which keeps them out of execution records at the source. Mark anything sensitive as secret in Netlify.
Can this connector cost real money?
It can consume paid capacity, and it says so where it happens. Netlify: Start Build and Netlify: Trigger Build Hook start real CI builds that consume the account's build minutes, and beyond the plan's included allowance Netlify charges for extra minutes. Netlify also rate-limits deploy-producing calls to 3 per minute and 100 per day. Netlify: Get Account Build Status exposes the build queue and the minutes counter so an automation can check usage before triggering anything.
How do I retry a failed deploy?
By starting a new build, because that is genuinely all Netlify offers: there is no retry endpoint in Netlify's API. Netlify: Start Build runs a fresh build of the site from its linked repository, optionally with clear_cache for failures that smell like stale dependencies, and the node's description says exactly that rather than pretending a retry primitive exists.
Can a Netlify deploy trigger a workflow?
Not as a trigger node in this connector; there is no inbound Netlify trigger. The honest pattern today is polling: run Netlify: List Site Deploys on a schedule, filter by state, and act on what changed. Build hooks run in the other direction: Netlify: Create Build Hook returns an unauthenticated URL that starts a Netlify build whenever anything POSTs to it, so your own systems can trigger deploys. The unguessable id in that URL is the only credential, so treat the URL itself as a secret; anyone holding it can start builds that consume build minutes.
Why did my token stop working?
Two usual causes. Netlify Personal Access Tokens carry an expiration date chosen when they are created, so long-lived automations eventually outlive their token. And a Netlify password reset revokes every existing token at once, so a security cleanup can silently break the connector. Either way, create a fresh token in User settings under Applications and update the credential on the connector.
Put Netlify to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Netlify is a product of its respective owner; Mattering is an independent platform.