Netlify
Connect Netlify to publish and roll back sites, trigger builds, manage environment variables, forms, domains and DNS, and check deploys.
You paste one value into PopMCP: a personal access token from your Netlify user settings (Applications, Personal access tokens). If your login belongs to several teams, you then choose which team the connection is for.
- Setup time
- 1 min
- Auth
- API credentials
- API base URL
- https://api.netlify.com/api/v1
- Rate limits
- About 500 requests a minute for most calls; deploys 3 a minute and 100 a day (Netlify API get started guide). Responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset; over a limit Netlify answers 429.
Before you begin
- A Netlify login. Personal access tokens are free on every Netlify plan, including the free one
- To change sites, deploys, environment variables or DNS, a team role that allows it (an Owner or Developer can do almost everything)
- If your team requires SAML single sign-on, be logged in to the team with SSO when you create the token
Get your credentials
Open Applications in your user settings
Sign in at app.netlify.com. Click your avatar, choose User settings, then Applications. The page opens on Personal access tokens.
Personal access tokens
Tokens let scripts and tools use the Netlify API as you.
No personal access tokens yet
Create one to use the Netlify API.
Name the token and choose when it expires
Click New access token. Enter a name that tells you what it is for, such as PopMCP. If your team uses SAML single sign-on, tick Allow access to my SAML-based Netlify team. Pick an Expiration date, then click Generate token. When the token expires, you connect again with a new one.
Personal access tokens
Tokens let scripts and tools use the Netlify API as you.
Copy the token
Netlify shows the token once, usually starting with nfp_. Copy it now: once you leave the page you cannot see it again. Then click Done.
Personal access tokens
Tokens let scripts and tools use the Netlify API as you.
Paste the token into PopMCP and choose the team
In PopMCP, paste the token into Personal access token and connect. PopMCP checks it and lists the Netlify teams your login belongs to; choose the team this connection is for (each team goes into its own workspace). The connection is then locked to that team.
Connect in PopMCP
Open your workspace, choose Netlify in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Personal access tokensecret | In Netlify: click your avatar, User settings, Applications, Personal access tokens, New access token. Give it a name, pick an expiration (and tick Allow access to my SAML-based Netlify team if your team uses single sign-on), Generate token, and copy it right away: Netlify shows it once. Stored encrypted.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Netlify immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP marks the Netlify connection Verified with your team's name and records your login's name, email and the team's plan. Asking the AI to list your sites returns them with their URLs and latest deploy.
Troubleshooting
"Netlify did not accept this token..."
Why: The token expired on the date chosen when it was made, it was copied incompletely, it was deleted, or your Netlify password was reset (that cancels every token).
Fix: Create a new token under **User settings**, **Applications**, **Personal access tokens** and connect again.
"Netlify refused this token. If your team uses SAML single sign-on..."
Why: The team requires SAML SSO and the token was made without access to it.
Fix: Log in to the team with SSO, create a new token with **Allow access to my SAML-based Netlify team** ticked, and connect with it.
"This Netlify login can no longer open the team..."
Why: You were removed from the team the connection was made for, or the team was deleted.
Fix: Ask a team Owner to add you back, or reconnect Netlify and choose another team.
A tool answers that the site belongs to a different Netlify team
Why: The site, deploy or DNS zone is in another team than the one this connection is locked to.
Fix: Connect that team too (it goes into its own workspace) and ask there, or pick a site of the connected team.
Tools fail with 429
Why: Netlify allows about 500 API requests a minute, and only 3 deploys a minute and 100 a day.
Fix: Wait a minute and retry. For many files, deploy once with deploy_files instead of one deploy per file.