mcp-devops-deploy
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-devops-deploy List all applications"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Deploy Automation
A Model Context Protocol (MCP) server for deployment automation. This server provides tools to manage deployments, environments, snapshots, and applications through DevOps Deploy's REST API.
Features
🚀 Quick Deployments: Deploy snapshots or specific component versions to any environment
📸 Snapshot Management: Create, list, and deploy snapshots
🌍 Environment Management: Discover and manage application environments
📊 Deployment Monitoring: Track deployment status and progress
⏰ Scheduling: Schedule deployments for future execution
🔄 Automation: Set up deployment triggers and recurring deployments
📋 Inventory Tracking: See what's deployed where and compare environments
Related MCP server: mcp-server-azure-devops
Prerequisites
Node.js 18.0.0 or higher
Access to an DevOps Deploy server
Valid Deploy server access token
Installation
npm install @securedevops/mcp-deploy-automationConfiguration
Set up environment variables or provide command line arguments:
Environment Variables
export DEPLOY_SERVER_URL="https://your-deploy-server:8443"
export DEPLOY_TOKEN="your-access-token"Best Practices
🔑 Use IDs Instead of Names
For better reliability and compatibility, always prefer using IDs over names when available:
Start with discovery tools: Use
list_applicationsto get application IDsGet environment IDs: Use
list_environments_for_applicationto get environment IDsGet snapshot IDs: Use
list_application_snapshotsto get snapshot IDsUse IDs in deployment operations: This avoids naming conflicts and ensures accuracy
Example workflow:
1. list_applications → Get application ID
2. list_environments_for_application → Get environment IDs
3. deploy_snapshot_to_environment using IDs instead of namesThe tools will display both names and IDs in their output, making it easy to copy the IDs for subsequent operations.
Example Use Cases
1. Automated Production Deployment
Scenario: You need to deploy a tested snapshot to production environment during a maintenance window.
Steps:
"List all applications to find my target application"
2. Environment Promotion Pipeline
Scenario: You need to promote code through development → staging → production environments.
Steps:
"Compare staging environment with production to see what changes are pending"
"Create a snapshot from the current staging environment called 'release-candidate-v2.1.4'"
"Deploy the snapshot to production environment using the 'Production Deploy' process"
"Monitor deployment status and ensure successful completion"
"Verify production inventory matches the deployed snapshot"
Benefits: Safe, controlled promotion through environments with full visibility and verification.
3. Scheduled Maintenance Deployment
Scenario: You need to schedule critical updates during off-hours maintenance windows.
Steps:
"List all environments for the 'Banking Platform' application"
"Schedule deployment of 'security-patch-v1.2.1' snapshot to production for tomorrow at 2:00 AM"
"Set up a deployment trigger for automatic rollback if deployment fails"
"Schedule weekly recurring deployments for the staging environment"
Benefits: Automated deployment scheduling reduces manual intervention and ensures deployments happen during optimal times.
Available Tools
1. deploy_snapshot_to_environment
Deploy a named snapshot to a specific environment.
Parameters:
application- Name or ID of the applicationsnapshot- Name or ID of the snapshot to deployenvironment- Name or ID of the target environmentapplicationProcess- Name or ID of the application processdescription(optional) - Description for the deploymentonlyChanged(optional) - Deploy only changed versions (default: true)
2. deploy_component_versions
Deploy specific component versions to an environment.
Parameters:
application- Name or ID of the applicationenvironment- Name or ID of the target environmentapplicationProcess- Name or ID of the application processversions- Array of component/version pairsdescription(optional) - Description for the deploymentonlyChanged(optional) - Deploy only changed versions (default: true)
3. list_application_snapshots
Get all available snapshots for an application.
Parameters:
application- Name or ID of the application
4. list_environment_inventory
Get current deployed versions in an environment.
Parameters:
application- Name or ID of the applicationenvironment- Name or ID of the environment
5. create_snapshot_from_environment
Create a new snapshot based on current environment state.
Parameters:
application- Name or ID of the applicationenvironment- Name or ID of the source environmentname- Name for the new snapshotdescription(optional) - Description for the snapshot
6. get_deployment_status
Check status of a running or completed deployment.
Parameters:
requestId- Request ID from a previous deployment
7. schedule_deployment
Schedule a deployment for future execution.
Parameters:
application- Name or ID of the applicationenvironment- Name or ID of the target environmentapplicationProcess- Name or ID of the application processdate- Date and time to schedule (yyyy-mm-dd HH:mm or unix timestamp)snapshot(optional) - Snapshot to deployversions(optional) - Component versions to deploydescription(optional) - Description for the deploymentrecurrencePattern(optional) - Recurrence: D (daily), W (weekly), M (monthly)
8. list_environments_for_application
Get all environments configured for an application.
Parameters:
application- Name or ID of the application
9. compare_environment_snapshots
Compare deployed versions between environments or against a snapshot.
Parameters:
application- Name or ID of the applicationsourceEnvironment- Name or ID of the source environmenttargetEnvironment(optional) - Name or ID of the target environmenttargetSnapshot(optional) - Name or ID of the target snapshot
10. create_deployment_trigger
Set up automated deployment triggers.
Parameters:
environment- Name or ID of the environmentname- Name for the deployment triggerapplicationProcess- Name or ID of the application processdescription(optional) - Description for the triggertriggerType- Type: VERSION_CHANGE or SCHEDULEschedulePattern(optional) - Schedule pattern for SCHEDULE triggers
11. list_applications
Get information about all applications on the server.
Parameters: None
Error Handling
The server provides detailed error messages and will indicate:
Authentication failures
Invalid application/environment names
Network connectivity issues
API response errors
Development
To run the server in development mode:
git clone https://github.com/securedevops/mcp-deploy-automation.git
cd mcp-deploy-automation
npm install
npm startLicense
ISC License
Contributing
Contributions are welcome! Please read our contributing guidelines and submit pull requests to our GitHub repository.
Support
For issues and questions:
GitHub Issues: https://github.com/securedevops/mcp-deploy-automation/issues
Documentation: https://github.com/securedevops/mcp-deploy-automation#readme
Available Tools
15 toolsauth_diagnosticsA
Run authentication diagnostics to determine current auth method and validity
Inputs: no named parameters.
compare_environment_snapshotsA
Compare deployed versions between environments or against a snapshot
Inputs: application (required), sourceEnvironment (required), targetSnapshot, targetEnvironment.
create_deployment_triggerC
Set up automated deployment triggers
Inputs: name (required), environment (required), triggerType (required), applicationProcess (required), +2 more.
create_snapshot_from_environmentB
Create a new snapshot based on current environment state
Inputs: name (required), application (required), environment (required), description.
deploy_component_versionsB
Deploy specific component versions to an environment
Inputs: versions (required), application (required), environment (required), applicationProcess (required), +2 more.
deploy_snapshot_to_environmentC
Deploy a named snapshot to a specific environment
Inputs: snapshot (required), application (required), environment (required), applicationProcess (required), +2 more.
get_component_versionsA
Get all versions for a specific component. Use this to find the version IDs needed for deployment.
Inputs: component (required), inactive, numResults.
get_deployment_statusA
Check status of a running or completed deployment
Inputs: requestId (required).
list_application_processesA
Get all application processes for a specific application. Use this to find the process needed for deployment.
Inputs: application (required).
list_applicationsA
Get information about all applications on the server. ALWAYS call this first to get application IDs before using any other deployment functions.
Inputs: no named parameters.
list_application_snapshotsA
Get all available snapshots for an application
Inputs: application (required).
list_componentsA
Get information about all components on the server. Use this to find components that can be deployed.
Inputs: active.
list_environment_inventoryB
Get current deployed versions in an environment
Inputs: application (required), environment (required).
list_environments_for_applicationA
Get all environments configured for an application. ALWAYS call this after list_applications to get environment IDs before deploying.
Inputs: application (required).
schedule_deploymentC
Schedule a deployment for future execution
Inputs: date (required), application (required), environment (required), applicationProcess (required), +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Deploy apps on your cloud. Create environments, configure infrastructure, and monitor jobs.
Deploy applications and manage governed Kubernetes preview spaces and capacity.
Manage Pipefork API projects, drafts, connections, secrets, and deployments through MCP.
Run AI models, create deployments, and manage predictions via cloud API
Related MCP Servers
- 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.-
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Azure DevOps, including listing pipelines and runs, viewing logs and artifacts, collecting and normalizing security reports, and triggering pipelines with safety controls.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to investigate threats, pull reports, manage security policies, and administer deployment infrastructure through the Cisco Secure Access REST API.-
- AlicenseNot gradedqualityDmaintenanceEnables management of Vercel projects, deployments, domains, environment variables, and teams via the Vercel REST API.MIT