Claude Netlify connectorWhat Claude can do in your Netlify account.
The Claude Netlify connector exposes 6 tools. 2 read your user and team details, 3 can change projects, deploys and extensions, and 1 is not documented anywhere. Below: what each one touches, what to approve, and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach your Netlify account
You stop switching between the chat where you wrote the code and the Netlify dashboard where it goes live. You describe the job in plain words, and Claude picks the Netlify tools it needs while it answers. You never call the connector by name: Netlify says Claude loads its tools only when the task calls for them.
Ship a project without leaving the chat. Once the code is ready, netlify-deploy-services carries the deploy side of the job and netlify-project-services the creation and upkeep of the project itself. Netlify's own examples cover starting a deploy and checking where your latest one stands.
Add a platform feature in one sentence. Need a Netlify extension on the site? netlify-extension-services installs it, or removes it when you are done testing.
Know who and what you are working with. netlify-user-services and netlify-team-services pull your account and team details, handy when you belong to several teams and forget which one owns a site.
Now what the directory sheet does not tell you. The tools are grouped by area, and Netlify never lists, tool by tool, which operations each group covers. One of the six, netlify-coding-rules, has no description at all. Nothing runs on its own either: no tool wakes up when a build fails or a form gets a new entry. That kind of background job belongs to an automation tool, a different trade: the Netlify n8n integration and the Netlify Make integration cover it.
The vocabulary in one minute
Five words you will meet while plugging Netlify into Claude.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in that account while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself, and the directory sheet lists them by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on. It is what lets an assistant like Claude talk to an outside service such as Netlify.
Connect Netlify to Claude in three steps
- 01
Find Netlify in Claude
In Claude, open Customize, then Connectors, and look for Netlify in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first, before each member can sign in.
- 02
Start the connection
Click Connect on the Netlify row, then sign in to Netlify in the window Netlify opens itself. If the link ever breaks, use Disconnect and connect again from the same place.
- 03
Read the authorization screen
Read the authorization screen before you accept it. It belongs to Netlify, not to Claude, and it sets what the access covers. You can also withdraw that access later from your Netlify account.
The 6 Claude Netlify connector tools, by what they do
Netlify gives Claude 6 tools: 2 that read your account, 3 that change something in it, and 1 no official source describes.
Three groups: what Claude reads, what it can change, and what no official source describes. Tool names stay exactly as Claude shows them.
- 2 read
- 3 write
- 1 not documented
What Claude reads (2)
2 toolsTwo tools that fetch account and team information.
netlify-user-services
Pulls the details of the Netlify account you connected, so Claude knows whose projects it is looking at before it goes any further.
netlify-team-services
Brings back information about your Netlify teams, so you can ask about a team in a sentence rather than three dashboard clicks.
What Claude can change (3)
3 toolsThree tools that act on your projects, deploys and extensions. No source describes a confirmation of their own: the general rule below applies.
netlify-deploy-services
Approval: see the ruleHandles the deploy side of your projects: Netlify's own examples show Claude starting a deploy and reporting the status of the latest one.
netlify-project-services
Approval: see the ruleCovers the life of a Netlify project, from creating it to keeping it in shape, and Netlify's examples include listing the projects you have.
netlify-extension-services
Approval: see the ruleAdds a Netlify extension to your setup, or takes one away, straight from the conversation.
Not documented (1)
1 toolThe directory publishes this name and nothing else. No official text says what it does, and we will not guess from a name.
netlify-coding-rules
This name sits in the directory's tool list, and that is all anyone publishes about it. Neither Netlify's docs nor its open repository describe it, so this page will not say more.
What Claude asks you before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request shows up in the chat, at the moment it matters.
On Team and Enterprise workspaces, owners decide whether members may let some actions through without being asked every time. They can also limit what a connector may do across the whole organization, for example keep reading open and close writing. That setting applies to everyone and nobody overrides it from their own account. And Claude works with your rights and nothing more: a site your Netlify login cannot open stays closed to it too. Netlify adds its own advice for that settings screen, summed up below.
Which plans it is available on
Out of the 819 sheets in the official directory, not one shows availability by plan. The per-connector answer is published nowhere: it is a real hole in the catalogue.
The general rule is published, though. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before each member can connect. For the current state on your account, the connector's own sheet in the official directory is the place to check.
Where the Claude Netlify connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a build fails, a form fills up or a domain expires.
This page rests on Netlify's own material only: no Claude help article covers this connector. The tool list is an observed floor, not a promise, since an admin can open actions that no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic says so on every sheet: it does not pick the tools a publisher exposes and does not vouch that they behave as announced. Connect what comes from a publisher you trust, here Netlify itself. For a connector where two official sources disagree, see the Claude gmail connector.
Need help connecting Netlify to Claude?
A person reads every message.
