Netlify MCP Server

Official

by netlify

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

netlify-extension-services-reader

Read-onlyIdempotent

Read Netlify extension data, fetch full extension details, or initialize the database to manage extension services.

Instructions

Select and run one of the following Netlify read operations (read-only) get-extensions, get-full-extension-details, initialize-database

Input Schema

TableJSON Schema

Name	Required	Description	Default
`selectSchema`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.3Oct 7, 2026

changedInput schema / properties / selectSchema / anyOf

Previous value: -[
-  {
-    "properties": {
-      "aiAgentName": {
-        "type": "string"
-      },
-      "llmModelName": {
-        "type": "string"
-      },
-      "operation": {
-        "const": "get-extensions",
-        "type": "string"
-      },
-      "params": {
-        "properties": {},
-        "type": "object"
-      }
-    },
-    "required": [
-      "operation"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "aiAgentName": {
-        "type": "string"
-      },
-      "llmModelName": {
-        "type": "string"
-      },
-      "operation": {
-        "const": "get-full-extension-details",
-        "type": "string"
-      },
-      "params": {
-        "properties": {
-          "extensionSlug": {
-            "type": "string"
-          },
-          "teamId": {
-            "description": "Team id of the current project team. If unsure, ask what Netlify team",
-            "type": "string"
-          }
-        },
-        "required": [
-          "extensionSlug",
-          "teamId"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "operation"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "aiAgentName": {
+        "type": "string"
+      },
+      "llmModelName": {
+        "type": "string"
+      },
+      "operation": {
+        "const": "get-extensions",
+        "type": "string"
+      },
+      "params": {
+        "properties": {},
+        "type": "object"
+      }
+    },
+    "required": [
+      "operation"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "aiAgentName": {
+        "type": "string"
+      },
+      "llmModelName": {
+        "type": "string"
+      },
+      "operation": {
+        "const": "get-full-extension-details",
+        "type": "string"
+      },
+      "params": {
+        "properties": {
+          "extensionSlug": {
+            "type": "string"
+          },
+          "teamId": {
+            "description": "Team id of the current project team. If unsure, ask what Netlify team",
+            "type": "string"
+          }
+        },
+        "required": [
+          "extensionSlug",
+          "teamId"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "operation"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "aiAgentName": {
+        "type": "string"
+      },
+      "llmModelName": {
+        "type": "string"
+      },
+      "operation": {
+        "const": "initialize-database",
+        "type": "string"
+      },
+      "params": {
+        "properties": {},
+        "type": "object"
+      }
+    },
+    "required": [
+      "operation"
+    ],
+    "type": "object"
+  }
+]

Changed3 schema fields changedv1.0.1Sep 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / selectSchema / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "aiAgentName": {
-        "type": "string"
-      },
-      "llmModelName": {
-        "type": "string"
-      },
-      "operation": {
-        "const": "get-extensions",
-        "type": "string"
-      },
-      "params": {
-        "additionalProperties": false,
-        "properties": {},
-        "type": "object"
-      }
-    },
-    "required": [
-      "operation"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "aiAgentName": {
-        "type": "string"
-      },
-      "llmModelName": {
-        "type": "string"
-      },
-      "operation": {
-        "const": "get-full-extension-details",
-        "type": "string"
-      },
-      "params": {
-        "additionalProperties": false,
-        "properties": {
-          "extensionSlug": {
-            "type": "string"
-          },
-          "teamId": {
-            "description": "Team id of the current project team. If unsure, ask what Netlify team",
-            "type": "string"
-          }
-        },
-        "required": [
-          "extensionSlug",
-          "teamId"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "operation"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "aiAgentName": {
+        "type": "string"
+      },
+      "llmModelName": {
+        "type": "string"
+      },
+      "operation": {
+        "const": "get-extensions",
+        "type": "string"
+      },
+      "params": {
+        "properties": {},
+        "type": "object"
+      }
+    },
+    "required": [
+      "operation"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "aiAgentName": {
+        "type": "string"
+      },
+      "llmModelName": {
+        "type": "string"
+      },
+      "operation": {
+        "const": "get-full-extension-details",
+        "type": "string"
+      },
+      "params": {
+        "properties": {
+          "extensionSlug": {
+            "type": "string"
+          },
+          "teamId": {
+            "description": "Team id of the current project team. If unsure, ask what Netlify team",
+            "type": "string"
+          }
+        },
+        "required": [
+          "extensionSlug",
+          "teamId"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "operation"
+    ],
+    "type": "object"
+  }
+]

Addedv1.0.0Jan 3, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, and the description's '(read-only)' merely repeats that. It adds no behavioral context such as authentication needs, rate limits, side effects of 'initialize-database', or what each operation touches, which is exactly what would be valuable here.

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?

One front-loaded sentence with no padding, which is appropriately sized for a dispatcher. It is slightly garbled by embedding the operation list inline and could have been structured as a short list, but nothing is wasted.

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 compound tool with a nested union schema and no output schema, the description should at minimum explain what each operation returns or requires. It omits per-operation semantics entirely, leaving the agent to reverse-engineer intent from const values.

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?

Schema description coverage is 0% and the single top-level parameter hides a discriminated union. The description only echoes the three operation consts that the schema already defines and says nothing about inputs like teamId or extensionSlug, so it adds almost no meaning beyond the structured field.

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

Purpose3/5

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

The description identifies a dispatcher that runs one of three named Netlify read operations, which is more specific than a tautology. However, it never explains what any of the three operations actually does (especially 'initialize-database', which reads like a mutating action), so an agent cannot distinguish their purposes or differentiate this tool from the sibling extension-services-updater beyond the word 'read'.

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?

It states the tool is for read operations but gives no guidance on when to pick get-extensions vs get-full-extension-details vs initialize-database, nor any condition under which the updater sibling should be chosen instead. The agent is left to infer selection entirely from the schema.

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

Deploy Server

netlify-extension-services-reader

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools