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
Server capabilities have not been inspected yet.
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-readerB | Select and run one of the following Netlify read operations (read-only) get-teams, get-team |
| netlify-project-services-readerA | 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
The tools are clearly organized by resource type (deploy, extension, project, team, user) and operation type (read vs. update), which minimizes ambiguity. However, the 'netlify-coding-rules' tool stands out as a special-purpose utility that doesn't fit neatly into this resource-based categorization, creating a minor point of potential confusion.
The naming follows a highly consistent pattern: 'netlify-[resource]-services-[operation]' for eight of the nine tools, with clear differentiation between 'reader' and 'updater' operations. The single outlier ('netlify-coding-rules') still maintains the 'netlify-' prefix, preserving overall naming coherence.
Nine tools is a reasonable number for a Netlify API server, covering multiple resource types and both read/write operations. It's slightly lean for comprehensive coverage of a platform like Netlify, but the scope appears well-defined around core deployment, project, and team management functions.
The server provides good read coverage for key resources (deploys, extensions, projects, teams, users) and write operations for some areas (deployments, extensions, projects). However, there are notable gaps: no update operations for teams or users, and missing common Netlify operations like site creation, function management, or build triggers that would be expected in a complete surface.