Netlify MCP Server

netlify-coding-rules

Define coding rules for Netlify projects to guide the creation of serverless functions, edge functions, blobs, and other resources before development.

Instructions

ALWAYS call when writing serverless or Netlify code. required step before creating or editing any type of functions, Netlify sdk/library usage, etc.

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": {
      "creationType": "<creationType>"
    },
    "name": "netlify-coding-rules"
  }
}

Input Schema

Name	Required	Description	Default
`creationType`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.0Jul 23, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only states it is a required step but does not disclose what the tool does (e.g., retrieve rules, set configuration, or have side effects). Missing critical behavioral context.

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

Conciseness4/5

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

The description is brief (two sentences) and front-loads the imperative 'ALWAYS call'. It is concise, though it could be more informative without being verbose.

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

Completeness2/5

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

For a tool described as 'required step', the description lacks details on output, side effects, and how it integrates with subsequent operations. No output schema exists, so the description should compensate. It does not.

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

Parameters1/5

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

The description does not mention the single parameter 'creationType' or explain its enum values. With 0% schema description coverage, the description should provide meaning, but it adds nothing, leaving the agent to infer from enum names alone.

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 clearly states this is a required preliminary step for serverless/Netlify coding, distinguishing it from sibling tools focused on services. The verb 'call' and resource 'coding-rules' are implied.

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

Usage Guidelines4/5

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

Explicitly says 'ALWAYS call when writing serverless or Netlify code' and identifies it as a required step before creating or editing functions. No alternatives mentioned, but the directive is clear.

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

Deploy Server