Netlify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETLIFY_ACCESS_TOKEN | Yes | Netlify personal access token for authentication |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| createSiteFromGitHubA | Create a new Netlify site from a GitHub repository |
| listSitesB | List Netlify sites |
| getSiteA | Get details of a specific site |
| deleteSiteB | Delete a site |
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
Each tool targets a distinct resource and action: create, list, get, and delete sites. There is no ambiguity because the operation and object are clearly named in each case.
All tool names follow a consistent verb+noun pattern in camelCase (e.g., listSites, getSite, deleteSite). Even createSiteFromGitHub follows the same style, just with a longer qualifier for the source.
Four tools is on the low end but still within a reasonable scope for a focused site management server. The set is not bloated, though it could benefit from a few more operations to feel complete.
The surface covers create, read (list/get), and delete, but notably lacks an update tool for modifying site settings or configuration. This is a significant gap for common site management workflows, though the core lifecycle covers the main operations.