mcp-devops-deploy
Related Servers
Alternatives to mcp-devops-deploy
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables management of Vercel projects, deployments, domains, environment variables, and teams via the Vercel REST API.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables searching and managing Docker images and tags, as well as querying GitLab CI/CD references, versions, and pipeline configurations through a DevOps API.-
- FlicenseCqualityBmaintenanceEnables management of Zadig CI/CD workflows, builds, services, environments, and webhooks through the Zadig OpenAPI.49-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to investigate threats, pull reports, manage security policies, and administer deployment infrastructure through the Cisco Secure Access REST API.-
- FlicenseNot gradedqualityCmaintenanceEnables interaction with Azure DevOps, including listing pipelines and runs, viewing logs and artifacts, collecting and normalizing security reports, and triggering pipelines with safety controls.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Vercel API to manage deployments, domains, projects, and environment variables.826 npmMIT
TDQS
Scored across 15 tools
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.
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.
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.
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.