A
licenseA
qualityD
maintenanceMCP server for managing Netlify sites, enabling operations such as creating sites from GitHub repositories, listing, viewing details, and deleting sites.
4
MIT
Netlify MCP Server
by MCERQUA
Related Servers
Alternatives to Netlify MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA serverless implementation of the Model Context Protocol (MCP) that runs on Netlify Functions, allowing developers to build and deploy MCP-compatible services with minimal configuration.ISC
Netlify MCP Serverofficial
AlicenseBqualityBmaintenanceEnables code agents to interact with Netlify services through the Model Context Protocol, allowing them to create, build, deploy, and manage Netlify resources using natural language prompts.1062,479 npm69ISC- AlicenseNot gradedqualityBmaintenanceEnables managing Netlify sites, deploys, builds, environment variables, and user information through MCP tools backed by the Netlify REST API.MIT
- AlicenseNot gradedqualityDmaintenanceA demonstration project for building and running Model Context Protocol (MCP) servers using Netlify Serverless Functions. It provides a template for deploying serverless MCP endpoints with automated CI/CD pipelines through Netlify.ISC
- AlicenseNot gradedqualityDmaintenanceDemonstrates how to deploy and run Model Context Protocol (MCP) servers using Netlify's serverless functions. Provides a basic example of serverless MCP implementation with customizable URLs and automated deployment pipeline.ISC
TDQS
B3.2/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: createSiteFromGitHub creates sites from GitHub, deleteSite removes sites, getSite retrieves details, and listSites lists all sites. There is no overlap in functionality, making tool selection unambiguous.
Naming Consistency4/5
Three tools follow a consistent verb_noun pattern (deleteSite, getSite, listSites), but createSiteFromGitHub deviates slightly by including 'FromGitHub' for specificity. This minor inconsistency does not hinder readability, as the naming remains intuitive and mostly uniform.
Tool Count3/5
With only 4 tools, the server feels thin for managing Netlify sites, as it lacks operations like updating sites, managing deployments, or handling environment variables. While the core CRUD operations are covered, the scope is limited and may require workarounds for common workflows.
Completeness3/5
The tools cover basic CRUD operations (create, read, delete, list) for sites, but there are notable gaps such as updating site settings, managing deployments, or handling other Netlify resources like functions or forms. This incomplete surface could lead to agent failures for advanced tasks.
Maintenance
ActivityInactive
ResponsivenessNo issues