Netlify MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| netlify-coding-rulesB | ALWAYS call when writing serverless or Netlify code. required step before creating or editing any type of functions, Netlify sdk/library usage, etc. |
| netlify-user-services-readerC | Select and run one of the following Netlify read operations (read-only) get-user |
| netlify-deploy-services-readerC | Select and run one of the following Netlify read operations (read-only) get-deploy, get-deploy-for-site |
| netlify-deploy-services-updaterC | Select and run one of the following Netlify write operations deploy-site |
| netlify-team-services-readerA | Select and run one of the following Netlify read operations (read-only) get-teams, get-team, get-team-env-vars |
| netlify-project-services-readerC | Select and run one of the following Netlify read operations (read-only) get-project, get-projects, get-forms-for-project |
| netlify-project-services-updaterC | Select and run one of the following Netlify write operations update-visitor-access-controls, update-forms, manage-form-submissions, update-project-name, manage-env-vars, create-new-project |
| netlify-extension-services-readerC | Select and run one of the following Netlify read operations (read-only) get-extensions, get-full-extension-details |
| netlify-extension-services-updaterC | Select and run one of the following Netlify write operations change-extension-installation, initialize-database |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Tools are clearly partitioned by domain (user, deploy, team, project, extension) and by read vs write intent, so their areas of responsibility are mostly distinct. The main ambiguity comes from each tool bundling multiple operations under a single selector, which forces the agent to infer which listed operation it actually needs.
All tools follow a consistent 'netlify-<domain>-services-<reader|updater>' pattern, reinforced by the reader/updater split. The only exception is netlify-coding-rules, which breaks the pattern but is still clearly named.
9 tools is within a reasonable scope for a Netlify management server. However, the count is somewhat misleading because many individual operations are compressed into category-level tools, making the real surface larger than the 9 tool names suggest.
The server covers core Netlify workflows: project management, deploys, env vars, forms, extensions, and basic user/team reads. Notable gaps include no team write operations, no project deletion, and no deploy listing or rollback capability, which may force agents to work around missing lifecycle steps.