Netlify MCP Server Status
Is the Netlify MCP server up? Live check of netlify-mcp.netlify.app, plus the fixes that solve most connection problems.
The check above sends the official Netlify MCP endpoint https://netlify-mcp.netlify.app/mcp the first request every MCP client sends. Up with HTTP 401 is the normal state: the server answers and asks for sign-in. If it is up and your connector still fails, work through the fixes below.
| MCP server URL | https://netlify-mcp.netlify.app/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth sign-in |
| Product | Netlify |
Netlify MCP not working? Fix it in this order
- Look at the live check above. If it says Down, the problem is on Netlify's side and usually clears up on its own; check again in a few minutes.
- Use the current URL:
https://netlify-mcp.netlify.app/mcp. - Sign in again. Netlify uses OAuth: tokens expire or get revoked when you change your password, leave a workspace or an admin removes access. Remove the connector and add it again, then finish the sign-in in the browser window that opens. In Claude Code:
claude mcp remove netlifyandclaude mcp add --transport http netlify https://netlify-mcp.netlify.app/mcp, thenclaude mcp listto see the state. - Ask your admin. In team and company workspaces an admin may have to allow the integration for Netlify before members can connect.
- Check the network. VPNs, company proxies and firewalls can block
netlify-mcp.netlify.app. Try another network to rule it out. - Update the client. Older clients only speak stdio or the old SSE transport. Current Claude, ChatGPT, Cursor and VS Code versions support remote servers over HTTP.
- Test it outside your client. Paste the URL into our MCP Server Tester to see exactly what the server answers.
Add Netlify MCP to your client
Claude (claude.ai, desktop): Customize, Connectors, + Add, Add custom connector, paste https://netlify-mcp.netlify.app/mcp. Claude Code: claude mcp add --transport http netlify https://netlify-mcp.netlify.app/mcp. Cursor: { "mcpServers": { "netlify": { "url": "https://netlify-mcp.netlify.app/mcp" } } }. VS Code: { "servers": { "netlify": { "type": "http", "url": "https://netlify-mcp.netlify.app/mcp" } } }.
Status of the other servers: MCP server status overview.
How it works
- Check the live status Up, including HTTP 401, means the server answers.
- Use the current URL https://netlify-mcp.netlify.app/mcp
- Reconnect Remove the connector, add it again and sign in.
FAQ
Is Netlify MCP down right now?
The live check at the top of this page tests https://netlify-mcp.netlify.app/mcp at most every five minutes. Up, including HTTP 401, means the server is answering.
What is the Netlify MCP server URL?
https://netlify-mcp.netlify.app/mcp.
Why is Netlify MCP not working in Claude or Cursor?
Most often an expired or revoked sign-in, an outdated URL or a blocked network. Remove the connector, add it again with the current URL and sign in again.
Why does Netlify MCP return 401?
Without a valid token every request gets 401, which is how the client knows it has to sign in. If you see 401 after signing in, the token expired or was revoked; reconnect.