Skip to main content
Glama
Sign In
mcp-cloud-deploy

mcp-cloud-deploy

by hoangtrietdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to mcp-cloud-deploy

No user-submitted related servers found.

    Related Servers

    • cloudflare-mcp

      Steph-ux
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a unified MCP interface to manage Cloudflare services including DNS, compute (Workers, KV, D1), storage (R2), AI, security, Radar, and a universal API gateway for any Cloudflare v4 endpoint.
      MIT

    • plint

      sladjanstojcic
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to deploy local static files to Bunny.net storage and pull zones, uploading only changed files, deleting removed ones, and purging the CDN cache. Also lets agents estimate deploy size and cost, list and inspect projects, view deployment history and files, and destroy projects through MCP tools.
      10 npm
      MIT

    • pocketnook

      shotintoeternity
      A
      license
      Not graded
      quality
      C
      maintenance
      Deploy GitHub repositories or local directories to private URLs directly from an MCP client. Includes tools for managing deployments, reading build logs, and stopping services.
      35 npm
      MIT

    • sitedrop

      t0saki
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for self-hosted static site publishing on Cloudflare Workers. Enables AI coding agents to deploy pages with a single 'publish' tool and get live URLs, with support for atomic updates, versioning, and per-site passwords.
      11 npm
      2
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have largely distinct primary actions (deploy, bind domain, list deployments). However, deploy_to_cloudflare_pages explicitly also binds custom domains and configures DNS, which overlaps with attach_custom_domain and could make an agent unsure which to use when a domain is supplied at deploy time.

    Naming Consistency4/5

    All names are snake_case with a leading verb (deploy_, attach_, list_) and target a Cloudflare Pages resource, giving a predictable pattern. deploy_to_cloudflare_pages is noticeably longer and adds a provider prefix the others omit, a minor deviation.

    Tool Count3/5

    Three tools is thin for a deployment server; the lifecycle of a Pages project typically involves more operations. The narrow scope (deploy static site, bind domain, list) is defensible but borderline minimal.

    Completeness3/5

    Core flow of deploy → bind domain → list is covered, but there are notable gaps: no rollback/retry, no delete or remove-domain, no project listing or deletion, and no access to build logs or deployment status details. Agents hitting failures would have no recovery tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources