Netlify
Netlify's own MCP server, shipped as @netlify/mcp, hands an agent nine tools for driving a Netlify account: readers and updaters for projects, deploys and extensions, readers for team and user info, and one tool that feeds Netlify coding rules back to the model. It runs over stdio and leans on whatever Netlify login already exists on the machine.
How we started it
npx -y @netlify/mcpUse it if you actually deploy to Netlify and want the agent to check a build, flip a project setting, or install an extension without you tabbing to the dashboard. The tool surface is small and the naming is consistent, which is rarer than it should be. The cost against it is the start: we measured 33,798 ms from spawn to a usable session, because npx fetches the package first, and a cold agent session that waits half a minute for one server will feel broken to whoever is watching.
Use it if
Skip it if
The bill for your context window
| Tool | Est. tokens | Described? | Required params |
|---|---|---|---|
| netlify-project-services-updater | ~942 | yes (188 chars) | 1 |
| netlify-project-services-reader | ~383 | yes (120 chars) | 1 |
| netlify-extension-services-updater | ~342 | yes (111 chars) | 1 |
| netlify-extension-services-reader | ~297 | yes (114 chars) | 1 |
| netlify-deploy-services-updater | ~290 | yes (72 chars) | 1 |
| netlify-deploy-services-reader | ~280 | yes (103 chars) | 1 |
| netlify-team-services-reader | ~250 | yes (91 chars) | 1 |
| netlify-user-services-reader | ~164 | yes (80 chars) | 1 |
The full tools/list payload is 12,332 bytes, about 3,083 tokens at the chars/4 estimate, measured 2026-08-19. That is a fair price for nine tools but the weight is not evenly spread: netlify-project-services-updater alone accounts for roughly 942 of those estimated tokens, because its schema enumerates every project setting you might change. The lightest, netlify-coding-rules, costs about 134. If you only ever read deploy status, you are still carrying the updater schemas around, and there is no way to ask the server for a subset.
Setup reality
Nothing exotic. The command is npx -y @netlify/mcp over stdio, and when we booted it under a clean environment with no secrets at all it still started and listed all nine tools, so no env var gate blocks initialization; the harness scraped no env hints from stderr. Authentication happens later, against your existing Netlify CLI login, which means the tools list is honest but the tools themselves will fail until that login exists. Two npm deprecation warnings scroll past on install, one for cron-parser and one for glob. Both are transitive and neither stops the server. Version reported by the server itself was 1.15.1 speaking protocol 2025-06-18.
Questions people ask
Why did the Netlify MCP server take so long to start?
We measured 33,798 ms on a cold run, and almost all of it is npx downloading @netlify/mcp and its dependency tree before the process even speaks JSON-RPC. Once the package is cached locally, subsequent starts skip the download. Pin the package globally if your client restarts servers often.
Do I need an API token in the environment?
No. It booted for us with a clean environment and no secrets, and reported no missing env vars. Auth is resolved through the Netlify CLI session on the machine, so tool calls need you to be logged in even though the server starts happily without it.
How many tools does it expose, and can I disable some?
Nine, split into readers and updaters across projects, deploys, extensions, team and user, plus a coding-rules tool. The server has no built-in filter, so hiding the updaters means whatever allow-list your MCP client supports.
Other cloud servers we started
| Server | Vendor | Boots | Context tax |
|---|---|---|---|
| Azure MCP | Microsoft | ✗ | ~0 tokens |
| Heroku | Heroku | ✗ | ~0 tokens |
| Kubernetes | community (Flux159) | ✓ | ~5,964 tokens |
How this page is made: the server is spawned as an unprivileged user with a clean environment and no credentials, then asked for its tools, resources and prompts over stdio. Token figures are estimates at four characters per token, not a tokenizer count. One run, one machine. Corrections: contact the desk.