What an agent can do in Netlify
Create and deploy sites, manage domains and environment variables, and inspect Netlify projects and deployments.
Jobs on Rush that use Netlify
- Which Leads Came In Through Each Client's Website This Week? A Web Design Agency's Netlify Forms Digest
- Which Campaign Links Are Sending Visitors to a 404? A Marketing Agency's Weekly Check of Client Sites on Netlify
How Netlify connects
Netlify is a remote MCP server, published by Netlify, at https://netlify-mcp.netlify.app/mcp. Connecting it signs in through the MCP OAuth flow on Netlify's side.
From Netlify: Netlify's MCP documentation · source code.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names netlify in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "Netlify",
"url": "https://netlify-mcp.netlify.app/mcp"
}Whose Netlify account the agent uses
Your Netlify connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Netlify, and a run started with an API key uses the Netlify of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Netlify, and that agent's runs use their account and nothing else: never yours, never another user's.
More Cloud integrations
Frequently asked questions
How do I connect Netlify to Rush?
Open Settings → Connections in the console and connect Netlify, or send POST /me/connections with {"type":"mcp","name":"Netlify","url":"https://netlify-mcp.netlify.app/mcp"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my Netlify account?
No. A run gets your Netlify connection only when it names it in connections ("connections": ["netlify"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in Netlify?
Create and deploy sites, manage domains and environment variables, and inspect Netlify projects and deployments. 2 published jobs use it; this page lists them.
Can my app's users connect their own Netlify?
Yes. Make each user an agent from your template, and they sign in to their own Netlify through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for engineering teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to