Netlify MCP Server
Server 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-servicesD | Select and run one of the following Netlify operations get-user |
| netlify-deploy-services | Select and run one of the following Netlify operations get-deploy, get-deploy-for-site, deploy-site |
| netlify-team-servicesD | Select and run one of the following Netlify operations get-teams, get-team |
| netlify-project-servicesC | Select and run one of the following Netlify operations get-project, get-projects, update-visitor-access-controls, update-forms, get-forms-for-project, manage-form-submissions, update-project-name, manage-env-vars, create-new-project |
| netlify-extension-services | Select and run one of the following Netlify operations change-extension-installation, get-extensions, get-full-extension-details, 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 4 tools
The three service tools (user, team, project) are distinct and target different resource types, but the netlify-coding-rules tool is confusing as it is a meta-instruction rather than an operation, potentially leading to misclassification.
Three tools follow a 'netlify-X-services' pattern, but netlify-coding-rules breaks this pattern by using 'rules' instead of 'services', introducing inconsistency.
With 4 tools, including one meta-tool, the count is slightly low for a platform like Netlify, but the bundling of many operations within the service tools compensates somewhat.
The set covers user, team, and project operations but lacks essential features like site management, deploys, and DNS, leaving significant gaps for typical Netlify workflows.