mcp-devops-deploy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEPLOY_TOKEN | Yes | Access token for the DevOps Deploy server | |
| DEPLOY_SERVER_URL | Yes | URL of the DevOps Deploy server |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deploy_snapshot_to_environmentC | Deploy a named snapshot to a specific environment |
| deploy_component_versionsB | Deploy specific component versions to an environment |
| list_application_snapshotsA | Get all available snapshots for an application |
| list_environment_inventoryB | Get current deployed versions in an environment |
| create_snapshot_from_environmentB | Create a new snapshot based on current environment state |
| get_deployment_statusA | Check status of a running or completed deployment |
| schedule_deploymentC | Schedule a deployment for future execution |
| list_environments_for_applicationA | Get all environments configured for an application. ALWAYS call this after list_applications to get environment IDs before deploying. |
| compare_environment_snapshotsA | Compare deployed versions between environments or against a snapshot |
| create_deployment_triggerC | Set up automated deployment triggers |
| list_applicationsA | Get information about all applications on the server. ALWAYS call this first to get application IDs before using any other deployment functions. |
| list_application_processesA | Get all application processes for a specific application. Use this to find the process needed for deployment. |
| list_componentsA | Get information about all components on the server. Use this to find components that can be deployed. |
| get_component_versionsA | Get all versions for a specific component. Use this to find the version IDs needed for deployment. |
| auth_diagnosticsA | Run authentication diagnostics to determine current auth method and validity |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.