Netlify MCP server

What the model can do

Netlify web hosting: sites with their URL, repository and last published deploy, deploys per site with state, branch, commit and error, the teams the token can see, and DNS zones and records. When you ask, can start a build, publish an earlier deploy again or roll back, cancel, lock, unlock or delete a deploy, and take a site offline or bring it back.

Reads

• netlify_list_sitesNetlify sites: name, URL, custom domain, team, repository and branch, and the last published deploy.
• netlify_list_deploysDeploys of one Netlify site: state (ready, error, building…), context (production, deploy-preview, branch-deploy), branch, commit…
• netlify_get_deployOne Netlify deploy by id: state, branch, commit, error message, timings and URL.
• netlify_list_teamsThe Netlify teams (accounts) this token belongs to, with the slug used to list their DNS zones.
• netlify_list_dns_zonesDNS zones managed by Netlify, optionally for one team (its slug).
• netlify_list_dns_recordsDNS records in one Netlify DNS zone: hostname, type, value and TTL.

Acts, when you ask

These change something in Netlify. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• netlify_create_buildStarts a Netlify build of a site from its linked repository.
• netlify_restore_deployPublishes an earlier deploy of a Netlify site again, replacing what is live for every visitor.
• netlify_rollback_deployRolls a Netlify site's production back to the deploy before the current one, changing the live site for every visitor.
• netlify_cancel_deployCancels a Netlify deploy that is still building or queued; it will not be published.
• netlify_lock_deployLocks a Netlify deploy so that later deploys of the site are built but not published.
• netlify_unlock_deployUnlocks a Netlify site's locked deploy, so new deploys publish automatically again (the next one will go live).
• netlify_delete_deployPermanently deletes a Netlify deploy (Netlify marks it for deletion); its preview URL stops working and it can no longer be restored.
• netlify_disable_siteDisables a Netlify site so it stops serving content: the site goes offline for every visitor until it is enabled again with netlify_enable_site.
• netlify_enable_siteRe-enables a Netlify site that was disabled by a user, so it serves content again for every visitor.

Connect it

First connect Netlify on Dashboard → Connections, then add Memtro to your client once. The Netlify tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Netlify connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Why did the last deploy of the marketing site fail?
• › What went live on Netlify today?
• › Which branch and commit is the docs site's production deploy built from?
• › Where does the www record for acme.com point?
• › Roll the marketing site back to its previous deploy

Questions

Is this an official Netlify MCP server?

No. It is Memtro's MCP server with Memtro's Netlify connector behind it: the connector reads Netlify through its API with the credentials you connect on Dashboard → Connections, and Netlify publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Netlify?

Only when you ask, and only what it has been granted: start a build and deploy of a site, to production unless a branch or draft is named; publish an earlier deploy of a site again; roll a site's production back to its previous deploy; cancel a deploy that is still building; lock a deploy so later deploys are built but not published, publishing it first if it is not live; unlock a site's locked deploy so new deploys publish again; delete a deploy; take a site offline for every visitor; bring a disabled site back online. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server