Netlify MCP Server

netlify-project-services

Create, retrieve, update, and manage Netlify projects with operations for access controls, forms, submissions, environment variables, and project naming.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selectSchema": "<selectSchema>"
    },
    "name": "netlify-project-services"
  }
}

Input Schema

Name	Required	Description	Default
`selectSchema`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.0Jul 23, 2026

TDQS

C2.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It only says 'select and run', disclosing no behavioral traits like side effects, idempotency, or permission requirements. Essential for a tool with multiple write operations (e.g., update-visitor-access-controls, manage-env-vars).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence listing operations. It is not overly long but could be more structured (e.g., using bullets or grouping). It is adequately concise but wastes the opportunity to add value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complex schema with 9 operations, many parameters, and no output schema, the description is incomplete. It does not explain the selectSchema router pattern, differentiate operations, or describe return behavior. A detailed description is critical here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no meaning beyond the schema. The schema has low coverage (0% as per signal) but includes some inline descriptions for nested parameters (e.g., projectNameSearchValue). The description merely lists operation names, failing to explain the selectSchema structure or how to choose parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the purpose: 'Select and run one of the following Netlify operations'. It lists the operations, making it clear it's a dispatch tool for project-related actions. However, it doesn't differentiate from sibling tools like netlify-team-services or netlify-user-services, missing an opportunity to clarify scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus siblings or alternatives. The description just lists operations without context about typical use cases, prerequisites, or when to avoid it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server