Skip to main content
Glama
fallegri

mcp-cloud-deploy

by fallegri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-cloud-deploy

No user-submitted related servers found.

    Related Servers

    • coolify-mcp

      jimrarras
      A
      license
      A
      quality
      B
      maintenance
      MCP server for managing a self-hosted Coolify instance. Provides full REST CRUD, deploy/watch capabilities, and an optional host-ops tier for live log streaming, SSH, Docker, and database access.
      22
      10 npm
      MIT

    • gemini-spark-mcp

      AditechIO7x
      F
      license
      Not graded
      quality
      C
      maintenance
      Deployable MCP server for GitHub and Vercel integration. Enables creating repos, pushing multiple files in a single commit, deploying projects to Vercel, managing environment variables, and combined deploy workflows via natural language.
      -

    • agent-deploy-dashbaord

      aparajithn
      A
      license
      Not graded
      quality
      D
      maintenance
      Unified deployment dashboard MCP server for AI agents. 9 tools to manage services across Vercel, Render, Railway, and Fly.io — deploy status, logs, service listing, environment variables, rollback, and health checks from one endpoint. Free tier: 50 requests/IP/day.
      3
      MIT

    • awesome-coolify-mcp

      clezcoding
      A
      license
      A
      quality
      A
      maintenance
      One MCP server to manage self-hosted Coolify instances: verify connectivity, discover servers, deploy applications, tail logs, diagnose incidents, and run emergency ops from any MCP client.
      19
      72 npm
      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

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct action and target: deploy to specific cloud providers, provision specific database types, local deployment modes, orchestration, and prerequisites checking. While deploy_to_vercel and deploy_to_railway share the deploy action, their distinct target platforms and descriptions eliminate ambiguity.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (provision_neon_database, orchestrate_deploy, check_deploy_prerequisites). Minor inconsistency: deploy_to_vercel and deploy_to_railway use 'to_' while deploy_docker_local and deploy_local omit it, but the patterns remain predictable and readable.

    Tool Count5/5

    8 tools is well-scoped for a deployment/provisioning server. Each tool covers a necessary part of the deployment lifecycle—cloud deploy, database provisioning, local deploy, orchestration, and prerequisites—without redundancy or bloat.

    Completeness4/5

    The tool set covers core deployment workflows: cloud deploy, database provisioning, local deployment (Docker and native), multi-service orchestration, and environment checks. Minor gaps include no teardown/destroy or status/listing tools, but these are not essential for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources