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.613,294-
- AlicenseCqualityDmaintenanceEnables AI agents to create, deploy, and manage Netlify projects and resources using natural language via the Netlify API and CLI.613,294ISC
- AlicenseNot gradedqualityDmaintenanceEnables natural language management of Cloudflare services including Workers, KV, R2, D1, Queues, and more via the Model Context Protocol.1,335Apache 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.9859MIT- AlicenseAqualityBmaintenanceEnables AI agents to build, edit, and publish live websites with hosting, database, auth, and domains via the Model Context Protocol.13111MIT
- AlicenseNot gradedqualityDmaintenanceManage Cloudflare resources such as Workers, KV, R2, D1, Durable Objects, and more using natural language via the Model Context Protocol.1,335Apache 2.0
TDQS
Scored across 9 tools
The tools are clearly organized by resource type (deploy, extension, project, team, user) and operation type (read vs. update), which minimizes ambiguity. However, the 'netlify-coding-rules' tool stands out as a special-purpose utility that doesn't fit neatly into this resource-based categorization, creating a minor point of potential confusion.
The naming follows a highly consistent pattern: 'netlify-[resource]-services-[operation]' for eight of the nine tools, with clear differentiation between 'reader' and 'updater' operations. The single outlier ('netlify-coding-rules') still maintains the 'netlify-' prefix, preserving overall naming coherence.
Nine tools is a reasonable number for a Netlify API server, covering multiple resource types and both read/write operations. It's slightly lean for comprehensive coverage of a platform like Netlify, but the scope appears well-defined around core deployment, project, and team management functions.
The server provides good read coverage for key resources (deploys, extensions, projects, teams, users) and write operations for some areas (deployments, extensions, projects). However, there are notable gaps: no update operations for teams or users, and missing common Netlify operations like site creation, function management, or build triggers that would be expected in a complete surface.