Netlify MCP Server
github.com/netlify/netlify-mcp- Category
- Developer Tools
- Rank
- No. 426Tools index
- Pricing
- Free
- Type
- TOOL
- Use case
- Deployment & Operations
- Interfaces
- MCP
- Builder
- netlify
- GitHub
- 63 stars
- Date
About
Netlify's official MCP server: create, deploy and manage sites from an agent — deploys, environment variables, forms and access controls without leaving the editor.
What it does
This server translates an agent’s natural-language requests into structured Netlify operations. It groups tools by project, deployment, team, user, and extension domains, separates reads from writes, authenticates locally or through remote bearer tokens, and returns API results for the agent to interpret.
Why it's ranked here
A strong pick for Netlify-centered agent workflows. Its scope reaches beyond publishing into forms, secrets, extensions, access rules, and account information. Read and write operations carry distinct annotations, authentication failures receive deliberate handling, and focused tests cover expired or invalid credentials. The documented runtime requirement is stricter than the code’s compatibility guard, however.
What's good
The tool design gives agents useful boundaries. Operations are grouped by domain and split into readers and updaters, while an optional verbose mode exposes each operation separately. Local authentication can reuse CLI credentials or a personal token. Remote requests accept bearer credentials, including encrypted tokens. Pagination has page and time limits, preventing unbounded API retrieval.
Tradeoffs
It assumes a Netlify account, an MCP client, and a recent Node runtime. The documentation asks for Node 22 or newer, while the runtime check only rejects versions below 20. Local authentication may invoke an interactive CLI login, and the CLI is recommended globally for the best experience. The listed domain plan leaves database operations, rollback selection, domains, and some settings uncovered.
How to use it well
Use it when a team already hosts on Netlify and wants an agent to handle routine project, deployment, account, form, secret, access, or extension work. Pair it with normal source control and human review for write operations. Do not treat it as a general database administrator or a complete deployment rollback system.
Technical notes+
package.json defines an ESM TypeScript package named @netlify/mcp, published with dist/* and a netlify-mcp binary built by tsup. src/tools/index.ts registers DomainTool definitions from project, deploy, team, user, and extension modules, partitions them through categorizeToolsByReadWrite, and supports grouped selector schemas or verbose per-operation registration. src/utils/api-networking.ts resolves local credentials from NETLIFY_PERSONAL_ACCESS_TOKEN or Netlify CLI configuration, handles remote bearer tokens and decrypted JWE payloads, and bounds pagination by page count and elapsed time. src/utils/compatibility.ts rejects Node versions below 20, although README.md requests Node 22 or higher. src/utils/api-networking.test.ts and src/utils/client-detection.test.ts cover authentication failure behavior and client recognition.
Observed
- License
- ISC
- Primary language
- TypeScript
- Packaging
- ES module npm package published as @netlify/mcp with an executable binary
- Install surface
- Runs through npx, with one-click configurations listed for several MCP clients
- Interface
- Model Context Protocol server bridging agents to the Netlify API and CLI
- Runtime
- README requires Node.js 22 or higher
- Testing
- Uses the built-in Node test runner with TypeScript test files
- Tool structure
- Operations are organized into project, team, user, deploy, and extension domains
Read from README.md, package.json, src/utils/cmd.ts, src/tools/index.ts, src/context/ctx.ts, src/tools/types.ts, src/utils/logging.ts, src/utils/version.ts, src/tools/tool-utils.ts, src/utils/compatibility.ts, src/utils/api-networking.ts, src/context/coding-context.ts, src/utils/client-detection.ts, src/utils/api-networking.test.ts, src/utils/client-detection.test.ts.
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.