Claude + Netlify: What the Integration Can (and Can't) Do in 2026
Yes — Netlify is an official Claude connector. It’s listed in Anthropic’s connectors directory (“Create, deploy, manage, and secure websites on Netlify,” marked Read & Write), backed by Netlify’s official MCP server. Turn it on and Claude can create and deploy sites, manage env vars and functions, and set access controls from a chat. The catch is the one every Claude MCP setup carries: it runs when you ask or on a schedule you set, never because something happened in Netlify. There are no triggers: a scheduled task can check your deploys every hour, but nothing reacts the moment a build fails.
Here’s exactly what the integration does, how to turn it on, where the limits bite, and what to use if you want Netlify work that runs on its own.
What the Netlify connector does
The connector wires Claude to your Netlify account through Netlify’s official MCP server, exposing site management, deploys, and configuration as tools you drive in natural language.
In practice, Claude can:
- Create and deploy sites — spin up a new site and push a deploy.
- Manage env vars and secrets — set and read environment variables and secrets.
- Handle serverless functions and forms — work with Functions, Edge Functions, and Netlify Forms.
- Set access controls — password-protect a site and manage access, plus extensions and other “agent skills” (Blobs, DB, Image CDN, caching, AI Gateway, framework adapters).
The everyday wins: “deploy this branch to a preview,” “add these env vars to production,” “password-protect the staging site.” All without leaving Claude.
How to set it up
Because Netlify is a first-party connector, the web/desktop path is a directory toggle rather than a hand-built server:
- In Claude, open Customize → Connectors and add Netlify from the directory (remote custom connectors on claude.ai require a paid plan).
- Authorize with your Netlify account via the browser OAuth flow.
- Back in a chat, ask Claude to deploy or configure a site; it hits Netlify’s MCP server on your behalf.
For Claude Code, Netlify documents a one-liner: claude mcp add --transport http netlify https://netlify-mcp.netlify.app/mcp (yes, the endpoint really is on netlify-mcp.netlify.app — it’s dogfooded on Netlify). There’s also an official local package, @netlify/mcp, that uses your Netlify CLI auth.
The limits that actually matter
The connector is genuinely good at pulling Netlify into a conversation. But its shape is “an operator you direct,” not “an agent that runs.” Three limits define it:
- No triggers. Claude runs when you ask or on a timer, and nothing in Netlify can start it. There’s no “redeploy when the CMS publishes” or “alert me the moment a build fails.” Netlify emits deploy webhooks, but the MCP server itself doesn’t act on them, so a failed build waits for your next prompt or the next scheduled run.
- Prompt or schedule only. Claude deploys when you ask or when a scheduled task fires; it doesn’t sit watching your pipeline and reacting to a failed build on its own.
- Clock-based, not event-based. Claude’s scheduled tasks run hourly, daily or weekly on paid plans, but they fire on a fixed clock, not on Netlify events. That’s not an always-on, event-driven deploy agent.
One automation note: Netlify caps deploy triggers at 3/min and 100/day via the API, so any “auto-deploy” flow has to respect that. Claude is great for “deploy this and set the env vars” — not for “guard every build and react when one breaks.”
If you want Netlify work that runs on its own: Carly
The moment you want something to happen around Netlify the instant it happens (email the team when a deploy fails, kick a build when content is published, capture a form submission and route it), you’ve crossed past what Claude’s connector is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- Fires on events, 24/7, in the cloud — hang a workflow off Netlify’s deploy notifications (deploy started/succeeded/failed, form submissions) or trigger a build via an incoming build hook; your laptop doesn’t need to be awake.
- Connects Netlify to the rest of your stack — take a failed deploy or a form submission and turn it into an email, a task, or a CRM record in the same workflow.
- Actually sends and updates — drafts and sends email (Gmail and Outlook) with attachments, files and labels, manages tasks, and updates your CRM.
- Builds the workflow for you — tell it “when a Netlify form comes in, email me the details and add the lead to my CRM” in plain English; it interviews you, then builds it with you. No prompt engineering.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free. Carly connects to 200+ tools across 40+ categories — see integrations. Netlify connects to Carly via your own API key — paste your Netlify personal access token on carlyassistant.com/integrations, and Carly can do whatever Netlify’s REST API allows.
Claude vs Carly
| Claude (Netlify connector) | Carly | |
|---|---|---|
| Deploy & manage sites | Yes | Yes |
| Set env vars & access controls | Yes | Yes |
| Acts on triggers / events | No | Yes |
| Reacts to a failed deploy on its own | No | Yes |
| Runs while you’re away | On a schedule only | Yes (on events) |
| Sends notifications as email | With your approval (Gmail) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude’s connector is a strong Netlify control panel inside a chat. Carly is a teammate that reacts to deploys and form submissions on its own.
Frequently Asked Questions
Does Claude work with Netlify?
Yes. Netlify is an official Claude connector in Anthropic’s directory (Read & Write), backed by Netlify’s official MCP server. Claude can create and deploy sites, manage env vars and functions, and set access controls inside a chat. Like all MCP setups, it runs when you ask or on a schedule you set, never because something happened in Netlify.
How do I connect Claude to Netlify?
In Claude, go to Customize → Connectors and add Netlify from the directory (remote custom connectors on claude.ai require a paid plan), then authorize over OAuth. For Claude Code, run claude mcp add --transport http netlify https://netlify-mcp.netlify.app/mcp. A local package, @netlify/mcp, uses your Netlify CLI auth.
Can Claude deploy automatically when I push or publish?
No. Claude runs when you ask or on a schedule you set, and there are no event triggers, so it won’t redeploy on a push or react to a failed build on its own. Netlify emits deploy webhooks and build hooks, but you need an agent platform like Carly to act on them 24/7.
Is this the same as Netlify Agent Runners?
No — keep them distinct. Agent Runners (launched Oct 2025) let Netlify host coding agents like Claude Code inside your dashboard against a live project. The MCP server is the reverse: your Claude agent controlling Netlify. This post is about the MCP connector.
More: Claude connectors · Claude + Vercel · Can Claude send emails · Claude vs Carly · Claude Cowork alternatives · Best AI tools for solopreneurs
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
