Skip to main content
Glama
netlify

Netlify MCP Server

Official
by netlify
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Netlify MCP Server

No user-submitted related servers found.

    Related Servers

    • Netlify MCP Server

      tharunkalluru
      -
      license
      C
      quality
      Not graded
      maintenance
      Follows 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.
      6
      56,216 npm
      -

    • cloudflare-mcp-server

      AmokOrg
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language management of Cloudflare services including Workers, KV, R2, D1, Queues, and more via the Model Context Protocol.
      2,120 npm
      Apache 2.0
    • @shiplohq/mcp by shiplohq

      @shiplohq/mcpofficial

      shiplohq
      A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to deploy static sites, track deployments, and manage sites on a Shiplo account through the Model Context Protocol.
      9
      24 npm
      MIT
    • Kleap by kleaphq

      Kleapofficial

      kleaphq
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to build, edit, and publish live websites with hosting, database, auth, and domains via the Model Context Protocol.
      13
      17 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tools are clearly partitioned by domain (user, deploy, team, project, extension) and by read vs write intent, so their areas of responsibility are mostly distinct. The main ambiguity comes from each tool bundling multiple operations under a single selector, which forces the agent to infer which listed operation it actually needs.

    Naming Consistency4/5

    All tools follow a consistent 'netlify-<domain>-services-<reader|updater>' pattern, reinforced by the reader/updater split. The only exception is netlify-coding-rules, which breaks the pattern but is still clearly named.

    Tool Count4/5

    9 tools is within a reasonable scope for a Netlify management server. However, the count is somewhat misleading because many individual operations are compressed into category-level tools, making the real surface larger than the 9 tool names suggest.

    Completeness3/5

    The server covers core Netlify workflows: project management, deploys, env vars, forms, extensions, and basic user/team reads. Notable gaps include no team write operations, no project deletion, and no deploy listing or rollback capability, which may force agents to work around missing lifecycle steps.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources