Skip to main content
Glama
humanagencyprotocol

@humanagencyp/deploy-mcp

Official
by humanagencyprotocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @humanagencyp/deploy-mcp

No user-submitted related servers found.

    Related Servers

    • ChangeWarden

      Mehdi1Hajjaji
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to request bounded GitHub changes through a default-deny policy, independent human approval, one-time execution with a GitHub App credential, and verifiable receipts.
      1
      -

    • ToolBridge

      Sehrabdar
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous AI agents to securely access and execute external tools, such as GitHub REST API operations, with per-user authentication, authorization, audit logging, and observability.
      MIT

    • Gatehouse

      ethanl05
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to request and perform registered deployment and login actions without exposing credentials, using local human approval and redacted verification receipts.
      6 npm
      1
      MIT

    • OpsMCP

      tanmays0
      F
      license
      A
      quality
      B
      maintenance
      Enables AI agents to safely interact with GitHub, query Postgres read-only, check deployment status, and search/read files within an allowlisted sandbox—all with dry-run writes and SQL/path safety gates.
      8
      -

    • Broker

      Abhishekvoid
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to securely perform privileged actions like creating GitHub issues by minting short-lived, single-purpose tokens on demand, with policy enforcement and audit logging.
      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.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: resolving a ref, listing deployments, getting a specific deployment, listing environments, and triggering a deploy. There is no overlap or ambiguity between the tools.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (resolve_ref, list_deployments, get_deployment, list_environments). 'deploy' is a single verb, which is a minor deviation but still understandable and consistent in style.

    Tool Count5/5

    The five tools are well-scoped for a deployment-focused server. Each tool covers a necessary part of the deployment workflow without being overly granular or redundant.

    Completeness4/5

    The core deployment lifecycle is covered: resolving a commit, deploying, listing, and getting deployments. Missing features like cancellation or rollback are minor gaps that do not critically hinder the main workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources