DeployHQ
Deployment made simple. We make it super easy to automate deploying projects from Git, SVN and Mercurial repositories.
Verdict
Common use cases
- Deploy hotfixes to production from chat
- Abort failed deployments mid-release
- Add build commands during sprint planning
- Exclude sensitive files from staging deploys
- Create config-only deployments for environment updates
Integration
- Vendor
- DeployHQ
- Category
- developer-tools
- Auth
- OAUTH2
- Tools
- 50
- Composio slug
deployhq
Tools
- Abort Deployment
Tool to abort a currently running deployment. Use when you need to terminate a deployment that is in progress.
- Add Project Repository
Tool to add repository details to a project in DeployHQ. Use when you need to configure a repository for a project with URL, SCM type, branch, and authentication credentials.
- Create Build Cache File
Tool to create a new build cached file within a project. Use when you need to add a new cached build artifact to the project's build cache storage.
- Create Build Command
Tool to create a new build command for a project in DeployHQ. Use when you need to add a new build command to a project.
- Create Config File
Tool to create a new config file in a DeployHQ project. Use when you need to add a configuration file that will be deployed to specified servers.
- Create Config File Deployment
Tool to create a new config file deployment for a project. Use when you need to deploy only configuration files to a server or server group without deploying code changes.
- Create Excluded File
Tool to add a new excluded file to a project. Use when you need to exclude specific files or patterns from deployment to prevent them from being deployed to servers.
- Create Project
Tool to create a new project in DeployHQ. Use when you need to initialize a new project with a name and optional zone configuration.
- Create Project Build Known Host
Tool to create a new known host in a project using DeployHQ API. Use when you need to add SSH known hosts for build processes in a specific project.
- Create Server
Tool to create a new server configuration in a DeployHQ project. Use when you need to add a deployment destination with protocol-specific settings (SSH, FTP, S3, etc.).
- Create Server Group
Tool to create a new server group for automated deployments in a DeployHQ project. Use when you need to set up a group of servers for deploying from a specific branch with auto-deploy and notification settings.
- Create SSH Command
Tool to create a new SSH command for a project in DeployHQ. Use when you need to add SSH commands that run before or after deployments.
- Delete Build Cache Filedestructive
Tool to delete an existing build cache file from a project. Use when you need to remove a cached build artifact from the project's build cache storage.
- Delete Commanddestructive
Tool to delete a command from a specified project. Use when you need to remove an SSH command from a project's configuration.
- Delete Excluded File Ruledestructive
Tool to delete an existing excluded file rule from a project. Use when you need to remove an excluded file pattern from deployment configuration.
- Delete Projectdestructive
Tool to delete a project from DeployHQ. Use when you need to permanently remove a project by its permalink or identifier.
- Delete Server Groupdestructive
Tool to delete a server group from a project using the DeployHQ API. Use when you need to remove a server group from deployment configuration.
- Delete Templatedestructive
Tool to delete a template by its unique permalink. Use when you need to permanently remove a template from DeployHQ.
- Generate AI Deployment Overview
Tool to generate an AI-powered deployment overview for a revision range. Use when you need to analyze commit messages between two references and get a concise summary of changes.
- Get Config File
Tool to view a specific config file in a DeployHQ project. Use when you need to retrieve details about a particular configuration file by its identifier.
- Get Excluded File
Tool to view a specific excluded file in a DeployHQ project. Use when you need to retrieve details about a particular excluded file by its identifier.
- Get Latest Repository Revision
Tool to view the latest remote revision of your repository. Use when you need to get the most recent commit hash for a project's default branch or a specific branch.
- Get Project
Tool to view an existing project in DeployHQ. Use when you need to retrieve details about a specific project by its permalink or identifier.
- Get Project Build Known Hosts
Tool to list all known hosts within a project using DeployHQ API. Use when you need to view SSH known hosts configured for a specific project.
- Get Project Commands
Tool to retrieve all SSH commands configured for a project. Use when you need to list all commands and their execution details for a specific project.
- Get Project Config Files
Tool to retrieve a list of all config files in a DeployHQ project. Use when you need to view all configuration files that are configured for a specific project.
- Get Project Deployments
Tool to retrieve a paginated list of all deployments in a project. Use when you need to view deployment history for a specific project. Results are paginated with 10 deployments per page.
- Get Project Excluded Files
Tool to list all excluded files within a project template. Use when you need to view which files or patterns are excluded from deployment for a specific project.
- Get Project Repository
Tool to view repository details for a specific project in DeployHQ. Use when you need to retrieve repository configuration including URL, branch, and hosting service details.
- Get Projects
Tool to retrieve all projects from DeployHQ account. Use when you need to list all available projects and their configurations.
- Get Project Scheduled Deployments
Tool to retrieve all upcoming scheduled deployments for a project. Use when you need to view scheduled deployment configurations including server details, revision information, frequency settings, and execution times.
- Get Project Server Groups
Tool to retrieve all server groups configured for a project. Use when you need to list servers and their deployment configurations within a project.
- Get Project Servers
Tool to retrieve all servers configured for a project. Use when you need to view server configurations and deployment targets for a specific project.
- Get Public Template
Tool to retrieve a specific public template from DeployHQ. Use when you need to view details of a public framework template using both template identifier and public template identifier.
- Get Public Templates
Tool to retrieve publicly available deployment templates from DeployHQ. Use when you need to list framework templates for popular web platforms.
- Get Recent Commits and Tags
Tool to view up to 15 most recent revisions and up to 15 most recent tags in a specific branch. Use when you need to retrieve recent commit history and tag information from a project's repository branch.
- Get Repository Branches
Tool to view all available branches in the connected repository for a project. Use when you need to list repository branches and their commit hashes.
- Get Repository Commit Info
Tool to view detailed information about a specific revision in a project's connected repository. Use when you need to retrieve commit details including author, timestamp, message, and tags.
- Get Server Group
Tool to view a specific server group in a DeployHQ project. Use when you need to retrieve details about a particular server group by its identifier.
- Get Templates
Tool to retrieve all templates from DeployHQ account. Use when you need to list all configured templates and their identifiers.
- Update Build Cache File
Tool to update an existing build cache file in a project. Use when you need to modify the path of a cached build artifact in the project's build cache storage.
- Update Build Command
Tool to update an existing build command in a project. Use when you need to modify the description, command, or error handling behavior of a build command. Supports partial updates - only include the fields you want to change.
- Update Config File
Tool to update an existing config file in a DeployHQ project. Use when you need to modify the path or contents of a configuration file.
- Update Excluded File
Tool to update an existing excluded file rule in a project. Use when you need to modify the file path pattern or server associations for an excluded file in the deployment configuration.
- Update Language Version
Tool to update the version of a language in a project's build environment. Use when you need to change the version of PHP, Node.js, Python, Ruby, Java, Go, .NET, or Composer used in a project's build pipeline.
- Update Project
Tool to update project settings in DeployHQ. Use when you need to modify a project's name or region/zone configuration.
- Update Project Command
Tool to update an existing SSH command in a project. Use when you need to modify command properties like description, command text, execution timing, timeout, or server assignments.
- Update Project Repository
Tool to update repository configuration for a project in DeployHQ. Use when you need to modify repository settings like branch, URL, SCM type, or authentication credentials.
- Update Server Group
Tool to update an existing server group in a DeployHQ project. Use when you need to modify settings such as name, branch, auto-deploy, notification preferences, or deployment mode. Supports partial updates - only include the fields you want
- Update Template
Tool to update an existing template in DeployHQ. Use when you need to modify the name or description of a template.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Developer Tools. 2. Find DeployHQ in the list and click Connect. 3. You'll redirect to DeployHQ's OAuth consent screen — sign in with your DeployHQ account. 4. Grant Switchy full access to your projects, deployments, and server configurations (DeployHQ uses a single scope for all operations). 5. After authorization, you'll return to Switchy with a green Connected badge next to DeployHQ. 6. Open any Space and type '@DeployHQ list my projects' to confirm the connection works. 7. If you see your project list, the integration is live. 8. To trigger a deployment, @mention DeployHQ with a project name and target server — the AI will invoke the appropriate tool and report status in the thread.
What teammates see: by default, memories from DeployHQ are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Active Projects
@DeployHQ show me all projects in my account with their current deployment statusOpen in a Space →
Deploy Latest Commit
@DeployHQ deploy the latest commit from the main branch of project 'web-app' to the production serverOpen in a Space →
Abort Running Deployment
@DeployHQ abort the deployment currently running for project 'api-service' and tell me what stage it was inOpen in a Space →
Add Build Command
@DeployHQ add a build command to project 'frontend' that runs 'npm run build' before every deploymentOpen in a Space →
Exclude Files from Deploy
@DeployHQ exclude all files matching '.env.local' and 'test/**' from deployments in project 'backend'Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@DeployHQ show me all active deployments across our projects and flag any that have been running longer than 10 minutes
Based on your DeployHQ account, I found 3 active deployments: 'api-service' to production (started 4 minutes ago, 67% complete), 'web-frontend' to staging (started 2 minutes ago, 23% complete), and 'worker-jobs' to production (started 14 minutes ago, stuck at 89% complete). The worker-jobs deployment exceeds your 10-minute threshold and may require attention. You can abort it using the deployment ID #847291 if needed.
This example demonstrates read-only monitoring across multiple projects. Requires OAuth scope to list deployments and projects. The MCP returns real-time deployment status, but completion percentages and timing depend on your actual deployment queue state at query time.
@DeployHQ create a new excluded file pattern to prevent .env.local files from being deployed to our production servers
I've added the exclusion pattern '.env.local' to your project's deployment configuration. This pattern will now prevent any .env.local files from being deployed to servers in this project. The exclusion is active immediately and will apply to all future deployments. You can verify this by checking your project's excluded files list in the DeployHQ dashboard.
This write action modifies your deployment configuration permanently. The exclusion applies project-wide unless you specify server groups. Be cautious: excluding critical files can break deployments. Always test exclusion patterns in staging before applying to production projects.
@DeployHQ review our last 5 failed deployments and summarize the common failure patterns so we can fix the root cause
Analyzing your last 5 failed deployments, I see a clear pattern: 4 of 5 failures occurred during the build command phase with 'npm install' timing out after 300 seconds. The fifth failure was a connection timeout to your staging server. Common thread: all failures happened between 2-4 PM UTC when your build server load is highest. Recommendation: increase your build command timeout from 5 to 10 minutes, or schedule deployments outside peak hours. The affected projects are 'web-frontend' (3 failures) and 'api-service' (2 failures).
This synthesis example combines deployment history retrieval with AI reasoning to identify patterns. The MCP provides raw deployment logs and status data; the AI interprets trends. Accuracy depends on having sufficient deployment history and detailed error logs in your DeployHQ account.
Use-case deep-dives
When DeployHQ wins for teams juggling staging and prod configs
A 6-person dev team ships to three environments (dev, staging, prod) and needs different database credentials, API keys, and feature flags in each. DeployHQ's config file tools let you version those files separately from code and deploy them independently. The Create Config File and Create Config File Deployment tools mean you can push a secrets update to staging without triggering a full code deploy. This works best when your config changes are more frequent than your code deploys—if you ship ten times a day, the overhead of managing 50 tools through OAuth starts to drag. For teams doing 2-5 deploys per day with environment-specific secrets, DeployHQ keeps config drift from becoming a post-mortem topic.
How DeployHQ handles the 'abort this now' moment in standups
Your 4-person product team just deployed a feature that's breaking checkout for 20% of users. Someone needs to abort the rollout, revert the build, and coordinate the fix across Slack while the PM updates stakeholders. DeployHQ's Abort Deployment tool gives you a programmatic kill switch—your AI workspace can trigger the abort, check deployment status, and log the incident without anyone SSH-ing into servers. The trade-off: if your rollback process involves more than stopping a deploy (like database migrations or cache purges), DeployHQ won't handle the orchestration. For straightforward code rollbacks at teams under 10 people, it turns a 15-minute scramble into a 90-second Slack thread.
When DeployHQ's build cache tools cut CI time for small teams
A 3-person startup runs a monorepo with shared frontend components that take 8 minutes to compile on every deploy. DeployHQ's Create Build Cache File and build command tools let you cache compiled assets and skip rebuilds when those directories haven't changed. This works if your build process is deterministic and you're deploying from a single branch—teams doing trunk-based development with 5+ daily merges see the biggest win. The ceiling: once your monorepo hits 50+ packages or your CI pipeline needs conditional caching logic, DeployHQ's 50-tool surface area becomes limiting. For early-stage teams with a monorepo under 20 packages, the build cache cuts deploy time in half without hiring a DevOps engineer.
Frequently asked
What does the DeployHQ MCP let me do in Switchy?
It connects your DeployHQ account so AI can manage deployments, configure repositories, create build commands, and handle config files. You can ask AI to abort a running deployment, add exclusion patterns, or set up a new project without opening the DeployHQ dashboard. Useful when you're troubleshooting a bad deploy or setting up CI/CD workflows through conversation.
Do I need admin access to connect DeployHQ via OAuth?
Yes. The OAuth flow requires account-level permissions to read projects, manage deployments, and modify build configurations. If you only have project-level access in DeployHQ, the connection will fail or return limited data. The person connecting this MCP should be an account owner or have full deployment management rights across all projects you want AI to touch.
Can the MCP automatically deploy code when I push to GitHub?
No. The MCP exposes DeployHQ's API for manual deployment control — aborting runs, creating config deployments, managing build commands. It doesn't set up webhook triggers or auto-deploy rules. For push-to-deploy automation, configure that directly in DeployHQ's project settings. Use the MCP when you want AI to intervene in deployments that are already configured.
How is this different from using DeployHQ's web UI or API directly?
The web UI requires clicking through forms to abort a deployment or add exclusion rules. The API requires writing scripts. The MCP lets you say "abort the staging deployment" or "exclude node_modules from the next deploy" in plain English. AI translates that into the correct API calls. Faster for one-off fixes; the UI is still better for setting up complex multi-stage pipelines.
Who on my team should connect this integration?
Whoever manages your deployment pipeline and has DeployHQ admin access. Once connected, any Switchy team member can ask AI to check deployment status or abort a bad release, but only the connected account's permissions apply. If your DevOps lead connects it, AI inherits their access. Don't connect it with a junior developer's account unless you want limited visibility.