Netlify MCP
Deploy, inspect, and manage Netlify sites, builds, environment configuration, and development workflows through Netlify's hosted MCP server.
Verdict
Common use cases
- Check deploy status during incident triage
- Trigger production builds from chat
- Review build logs when CI fails
- Update environment variables for feature flags
- Confirm site uptime before customer demos
Integration
- Vendor
- Netlify MCP
- Category
- developer-tools
- Auth
- OAUTH2
- Composio slug
netlify_mcp
Tools
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Netlify MCP in the developer tools section and click Connect. 3. You'll redirect to Netlify's OAuth consent screen — sign in with the account that owns the sites you want to manage. 4. Grant the requested scopes, which typically include read access to sites and deploys, plus write access for triggering builds and updating environment variables. 5. Netlify redirects you back to Switchy with a success confirmation. 6. Open any Project and type '@Netlify list my sites' to verify the connection — you should see your active sites returned in the chat. 7. If the response is empty or errors, revisit Settings > Integrations to reconnect or check that your Netlify account has sites deployed.
What teammates see: by default, memories from Netlify MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Active Sites
@Netlify show me all active sites in our account, including their URLs and last deploy time.
Check Deploy Status
@Netlify what's the status of the most recent deploy for our production site? Include any error messages if it failed.
Trigger New Deploy
@Netlify trigger a new deploy for our main site using the current branch.
Fetch Build Logs
@Netlify get the build logs for the most recent deploy that failed on our staging site.
Update Environment Variable
@Netlify update the FEATURE_FLAG_NEW_CHECKOUT environment variable to 'true' on our production site.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Netlify list all my sites and show me which ones have failed builds in the last 24 hours
Based on your Netlify account, you have 12 active sites. Two sites show failed builds in the last 24 hours: 'marketing-site' (failed 3 hours ago with exit code 1 during npm build) and 'docs-preview' (failed 18 hours ago due to a missing environment variable). The remaining 10 sites have successful builds, with 'app-production' last deployed 6 hours ago.
This example demonstrates read access to site status and build history. Requires OAuth scope for reading site and deploy data. The MCP queries Netlify's API for build logs and timestamps — useful for morning standup checks, but won't show builds from team members' personal accounts unless you have org-level access.
@Netlify trigger a new production deploy for my 'app-production' site using the latest commit from main branch
Deploy triggered for 'app-production'. Build ID: 6f8a3c2d-4e91-4b5a-9c3e-7d2f1a8b9e0c. Netlify is now pulling the latest commit (sha: a3f7c21) from your main branch and running the build command. Estimated completion: 3-5 minutes. You can monitor progress at https://app.netlify.com/sites/app-production/deploys/6f8a3c2d.
This write action requires OAuth scope for triggering deploys. Side-effect: initiates a billable build minute and publishes to production when complete. Use cautiously in shared Projects — consider restricting this MCP to admin-only channels if multiple teammates have access. No rollback is automatic if the deploy introduces issues.
@Netlify check the last 5 form submissions on my 'contact-us' site and summarize any that mention 'enterprise pricing'
Reviewed 5 form submissions from the past 48 hours on 'contact-us'. Two mention enterprise pricing: (1) Sarah Chen from Acme Corp asked about volume discounts for 50+ seats, submitted yesterday at 2:14 PM. (2) James Liu from Beta Industries requested a custom contract quote, submitted today at 9:03 AM. Both provided email addresses. The other three submissions were general inquiries about product features.
This synthesis example pairs Netlify's form data with AI reasoning to filter and summarize. Requires OAuth scope for reading form submissions. Be aware that form data may contain PII — ensure your Switchy Project's access controls align with your privacy policies. Netlify's free tier caps form submissions at 100/month.
Use-case deep-dives
When Netlify MCP speeds up async design feedback loops
A 5-person product team runs weekly design reviews where the designer shares Figma mocks and the engineer shares a live deploy preview. Without the MCP, the engineer copies the Netlify URL from Slack, pastes it into the doc, and manually checks build status. With OAuth connected, Switchy pulls the preview URL and build logs directly into the review thread—no tab-switching. The win is real if your team ships 3+ previews a week and design-eng handoff happens in shared docs. If you're solo or only deploy to production, the overhead of OAuth setup outweighs the saved clicks. This is for teams where deploy previews are a collaboration artifact, not just a CI step.
Why Netlify MCP matters when production breaks at 2am
A 3-person startup wakes up to a broken production site. The on-call engineer needs to compare the last three deploy logs, check environment variables, and roll back if needed. Normally this means logging into Netlify's dashboard, clicking through deploy history, and copy-pasting error traces into Slack. The MCP lets Switchy surface recent deploys, pull logs, and trigger rollbacks from the incident channel—all without leaving the conversation. The threshold: if you deploy less than twice a day or your incidents are rare, the MCP is overkill. But if you're shipping continuously and your team triages in shared threads, having deploy context inline cuts mean-time-to-resolution by 10-15 minutes per incident.
When Netlify MCP helps agencies close projects faster
A 6-person agency builds client sites on Netlify and hands off a runbook at project end. The account manager needs to document live URLs, form endpoints, environment variables, and DNS settings—data that lives in Netlify's dashboard. Manually screenshotting and writing this takes 45 minutes per project. With the MCP, Switchy queries the site config and auto-generates the handoff doc in 5 minutes. The catch: if you only close 1-2 projects a quarter, the OAuth setup isn't worth it. But agencies closing 6+ sites a year save 4-5 hours annually and reduce handoff errors. This is for teams where Netlify config is a deliverable, not just internal infrastructure.
Frequently asked
What does the Netlify MCP do in Switchy?
The Netlify MCP connects your team's Netlify account to Switchy's AI workspace, letting Claude access deployment data, site configurations, and build logs. Your team can ask questions about deploy status, troubleshoot build failures, or review site settings without switching to the Netlify dashboard. It's useful for teams running static sites or JAMstack apps who want AI assistance with their hosting infrastructure.
Do I need admin access to connect Netlify via OAuth?
You'll need owner or collaborator permissions on the Netlify team you're connecting. The OAuth flow requests read access to sites, deploys, and build logs by default. If the MCP supports write operations later, you'd grant additional scopes during setup. Check your Netlify team settings before connecting to avoid authorization failures.
Can the Netlify MCP trigger new deploys or roll back sites?
That depends on which tools the MCP exposes and which OAuth scopes it requests. Most read-only MCPs let Claude inspect deploy history and site config but can't trigger builds. If you need deploy control, verify the MCP requests write scopes during OAuth setup. Otherwise, use Netlify's API directly or their CLI for production changes.
How is this different from just using the Netlify dashboard?
The MCP lets Claude pull Netlify data into conversations without you manually copying deploy IDs or build logs. You can ask 'why did the last deploy fail' and get an answer grounded in actual logs, or compare site configurations across projects in one prompt. It's faster for troubleshooting and audits, but the dashboard remains better for visual workflows like form management or split testing.
Who on the team should connect the Netlify MCP?
Whoever owns your Netlify account or has collaborator access to the sites you want Claude to see. Once connected, any Switchy workspace member can query Netlify data through Claude, so connect it once and share access. The connection doesn't consume extra Netlify seats, but check your Switchy plan if you're adding multiple integrations.