Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Netlify to Claude Code

Let Claude trigger deploys and manage env vars in Netlify. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Netlify to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Netlify, you add a Netlify MCP server: a small hosted service that exposes Netlify's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Netlify account. No API keys pasted into config files.

claude mcp add --transport http netlify https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Netlify once connected?

Full read-write Netlify access lets Claude trigger a build or deploy, roll back to a previous deploy, set or update environment variables, manage form submissions, and read deploy logs to diagnose a failure. The work that used to mean switching to the dashboard or CLI happens where you are already chatting.

  • Trigger a new build or deploy for a specific site
  • Roll back a site to a previous successful deploy
  • Set, update, or remove environment variables on a site
  • Read deploy logs and surface the cause of a failed build
  • Create or update a deploy hook for a branch
  • List and export form submissions for a site

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Netlify access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Netlify API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Netlify changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Netlify connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Netlify connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Netlify account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Netlify's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Netlify?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Netlify account it signs in with. Revoking access is one click in Netlify.

More on the Netlify connector

Netlify connector for claude.aiBitbucket + Claude CodeCircleCI + Claude CodeJenkins + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us