mcpbeat Sign in

Netlify MCP Server

answering

Netlify is answering right now. Last checked 10 min ago.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
734 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Netlify every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add mcp --transport http https://netlify-mcp.netlify.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://netlify-mcp.netlify.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://netlify-mcp.netlify.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://netlify-mcp.netlify.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://netlify-mcp.netlify.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://netlify-mcp.netlify.app/mcp streamable-http sign-in 378 ms 10 min ago

Alternatives to Netlify

same job, measured the same way
Mintlify
by mintlify
answering
Neon
by neon
answering
Netdocuments
by netdocuments
answering
V
Spotify
by spotify
answering
Shopify
by shopify
26 tools answering
Clarify
by clarify
answering

Netlify — questions

Answers built from our own checks of this server.

Why is there no tool list for Netlify?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Netlify working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 734 ms. The bar chart above shows every period we have measured.
How do I connect Netlify?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Netlify?
No API key is involved. Netlify answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Netlify?
It answers our handshake in 734 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.