Netlify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETLIFY_PERSONAL_ACCESS_TOKEN | No | Your Netlify Personal Access Token (PAT) 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-netlify-coding-contextB | ALWAYS call when writing serverless or Netlify code. required step before creating or editing any type of functions, Netlify sdk/library usage, etc. |
| ntl-user-operationsD | Run one of the following operations get-user |
| ntl-deploy-operationsC | Run one of the following operations get-deploy, get-deploy-for-site, deploy-site |
| ntl-team-operationsC | Run one of the following operations get-teams, get-team |
| ntl-project-operationsD | Run one of the following 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 |
| ntl-extension-operationsD | Run one of the following 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 6 tools
The tools are grouped by resource type (deploy, extension, project, team, user), which provides some clarity, but the grouping approach creates ambiguity within each tool. For example, 'ntl-project-operations' bundles 9 different operations under one tool name, making it impossible for an agent to distinguish between them without reading the description. This forces the agent to parse the description to understand available actions, rather than having distinct tools for each operation.
Most tools follow a consistent 'ntl-[resource]-operations' pattern (e.g., ntl-deploy-operations, ntl-project-operations), which is predictable. However, 'get-netlify-coding-context' deviates from this pattern, using a verb-noun format instead. This minor inconsistency reduces the overall naming coherence, but the majority of tools adhere to a clear convention.
With 6 tools, the count is reasonable for a Netlify server, covering key areas like deployments, extensions, projects, teams, and users. It's slightly lean given the bundled operations, but each tool represents a logical domain, making the scope manageable. A few more tools could provide better granularity, but this is not a significant issue.
The server covers core Netlify domains (deployments, projects, teams, users, extensions) but has notable gaps. For example, there are no tools for creating or deleting deployments, managing site settings, or handling build operations. The bundled operations within tools suggest some coverage, but the surface is incomplete for full lifecycle management, which may cause agent failures in complex workflows.