Skip to main content
Glama
mrchris2000

mcp-devops-deploy

by mrchris2000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-devops-deploy

No user-submitted related servers found.

    Related Servers

    • vercel-mcp

      amerilain
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables management of Vercel projects, deployments, domains, environment variables, and teams via the Vercel REST API.
      MIT

    • Octopus Deploy Official MCP

      AnkitMoon886
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to inspect, query, and diagnose problems in a continuous delivery platform, and to perform release, deployment, runbook, task, tenant, and related operational actions with configurable read-only or write access.
      266 npm
      MIT

    • zadig-mcp

      Deraiven
      F
      license
      C
      quality
      B
      maintenance
      Enables management of Zadig CI/CD workflows, builds, services, environments, and webhooks through the Zadig OpenAPI.
      49
      -

    • Cisco Secure Access MCP Server

      ACSmith1337
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to investigate threats, pull reports, manage security policies, and administer deployment infrastructure through the Cisco Secure Access REST API.
      -

    • mcp-server-azure-devops

      abhi-d-git
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Azure DevOps, including listing pipelines and runs, viewing logs and artifacts, collecting and normalizing security reports, and triggering pipelines with safety controls.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, with clear separation between snapshots, components, environments, and deployments. The only real overlap is between create_deployment_trigger and schedule_deployment, both of which set up future deployments and could be misselected.

    Naming Consistency4/5

    The large majority follow a consistent verb_noun pattern such as list_applications, deploy_component_versions, and get_deployment_status. Minor deviations like auth_diagnostics and create_deployment_trigger break the pattern slightly, but the naming remains predictable overall.

    Tool Count4/5

    Fifteen tools is at the upper boundary of a well-scoped deployment server, and each tool covers a distinct facet of the deployment workflow. A few tools such as auth_diagnostics and create_deployment_trigger feel slightly peripheral, but none seem redundant enough to cut.

    Completeness3/5

    Core deployment workflows are covered well: listing applications/components/environments, deploying snapshots or component versions, scheduling, and checking status. Notable gaps include no way to cancel or roll back a deployment, and triggers/snapshots only support creation with no update/delete lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources