multi-account-netlify-mcp
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 | {} |
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 Multi-account (the account argument): get-user: every named account answers. |
| netlify-deploy-services-readerA | Select and run one of the following Netlify read operations (read-only) get-deploy, get-deploy-for-site Multi-account (the account argument): get-deploy: only the account that owns the id answers, and accounts without it are listed under notFoundIn; get-deploy-for-site: only the account that owns the id answers, and accounts without it are listed under notFoundIn. |
| netlify-deploy-services-updaterC | Select and run one of the following Netlify write operations deploy-site Multi-account (the account argument): deploy-site: one account only, so a list or all is refused. |
| netlify-team-services-readerA | Select and run one of the following Netlify read operations (read-only) get-teams, get-team, get-team-env-vars Multi-account (the account argument): get-teams: every named account answers; get-team: only the account that owns the id answers, and accounts without it are listed under notFoundIn; get-team-env-vars: only the account that owns the id answers, and accounts without it are listed under notFoundIn. |
| netlify-project-services-readerA | Select and run one of the following Netlify read operations (read-only) get-project, get-projects, get-forms-for-project Multi-account (the account argument): get-project: only the account that owns the id answers, and accounts without it are listed under notFoundIn; get-projects: every named account answers; get-forms-for-project: only the account that owns the id answers, and accounts without it are listed under notFoundIn. |
| netlify-project-services-updaterB | 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 Multi-account (the account argument): update-visitor-access-controls: one account only, so a list or all is refused; update-forms: one account only, so a list or all is refused; manage-form-submissions: get-submissions needs the account that owns the form (only it answers); delete-submission needs one account; update-project-name: one account only, so a list or all is refused; manage-env-vars: listing needs the account that owns the site (only it answers); creating, updating and deleting need one account; create-new-project: one account only, so a list or all is refused. |
| netlify-extension-services-readerA | Select and run one of the following Netlify read operations (read-only) get-extensions, get-full-extension-details, initialize-database Multi-account (the account argument): get-extensions: every named account answers; get-full-extension-details: only the account that owns the id answers, and accounts without it are listed under notFoundIn; initialize-database: every named account answers. |
| netlify-extension-services-updaterB | Select and run one of the following Netlify write operations change-extension-installation Multi-account (the account argument): change-extension-installation: one account only, so a list or all is refused. |
| netlify-observability-services-readerC | Select and run one of the following Netlify read operations (read-only) get-counts, get-topk, get-timeseries, get-request-logs, get-request-detail Multi-account (the account argument): get-counts: only the account that owns the id answers, and accounts without it are listed under notFoundIn; get-topk: only the account that owns the id answers, and accounts without it are listed under notFoundIn; get-timeseries: only the account that owns the id answers, and accounts without it are listed under notFoundIn; get-request-logs: only the account that owns the id answers, and accounts without it are listed under notFoundIn; get-request-detail: only the account that owns the id answers, and accounts without it are listed under notFoundIn. |
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 10 tools
Each tool is scoped to a distinct Netlify domain (user, deploy, team, project, extension, observability) and cleanly split into read vs. write, so boundaries are clear. The only ambiguity is that each tool multiplexes many sub-operations internally, and netlify-coding-rules overlaps thematically with everything as a pre-step advisory tool.
Tools follow a strong, predictable pattern: netlify-<domain>-services-<reader|updater>, which makes read vs. write obvious at a glance. The lone outlier is netlify-coding-rules, which breaks the pattern but is clearly a different kind of tool.
Ten tools is well-scoped for a multi-domain Netlify server, and the dispatcher pattern lets each tool cover several operations without surface bloat. No tool feels redundant or padded.
Read coverage is thorough across user, deploy, team, project, extension, and observability, and core writes exist (deploy-site, create-new-project, manage-env-vars, forms, extension install change). Notable gaps remain, including team/member management writes, project or site deletion, and DNS management, but agents can work around most of these.