Netlify MCP Server
OfficialRelated Servers
Alternatives to Netlify MCP Server
No user-submitted related servers found.
Related Servers
- -licenseCqualityNot gradedmaintenanceFollows the Model Context Protocol to enable code agents to use Netlify API and CLI, allowing them to create, deploy, and manage Netlify resources using natural language prompts.624,307 npm-
- AlicenseCqualityDmaintenanceEnables AI agents to create, deploy, and manage Netlify projects and resources using natural language via the Netlify API and CLI.624,307 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables natural language management of Cloudflare services including Workers, KV, R2, D1, Queues, and more via the Model Context Protocol.1,577 npmApache 2.0

@shiplohq/mcpofficial
AlicenseAqualityBmaintenanceEnables AI clients to deploy static sites, track deployments, and manage sites on a Shiplo account through the Model Context Protocol.92 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access file systems, fetch web content, query databases, and execute shell commands through the standardized Model Context Protocol.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to build, edit, and publish live websites with hosting, database, auth, and domains via the Model Context Protocol.138 npm1MIT
TDQS
Scored across 10 tools
The tools are mostly distinguished by Netlify service area and read/write role, so an agent can usually tell them apart. However, the extension reader includes a write-like 'initialize-database' operation, and several tools bundle multiple sub-actions behind a single 'select and run' interface, which adds some ambiguity.
Almost all tools follow a consistent kebab-case pattern: netlify-<service>-services-<reader|updater>. The only deviation is netlify-coding-rules, which does not match the service/read-write convention but is still readable and clearly distinct.
Ten tools is a well-scoped set for Netlify management, covering multiple service areas without becoming overwhelming. Each tool maps to a coherent service-and-access pattern rather than an arbitrary grab bag.
The server covers read/write operations across deploys, projects, teams, users, extensions, and observability, which is broad coverage for common Netlify workflows. There are still apparent gaps around destructive operations and some specialized site configuration areas, but core lifecycle tasks are represented.