list_projectsLABSCO SUMMARY
The deployment log is a tool, which is the difference between deploying and debugging.
Triggering a deploy is easy; the useful part is that when it fails the assistant can pull the full log and tell you what broke without you opening the dashboard. Preview mode on create_deployment is worth knowing about — it lets you see what a commit range would do before queueing it for real.
What it is
A DeployHQ server covering projects, servers and deployments, plus the account-level pieces deployments depend on: SSH keys, global environment variables and config file templates.
What you get
- list_projects and get_project — projects with their repository information and deployment status
- list_servers — the servers configured for a project
- list_deployments and get_deployment — deployments with pagination and per-server filtering, and one deployment in detail
- get_deployment_log — the complete deployment log as text, which is where a failure explains itself
- create_deployment — deploy a commit range to a server or server group, with options for branch, queue or preview mode, config file copying, build commands and the build cache
- list_ssh_keys and create_ssh_key — account SSH keys, listed with fingerprints and never returning private keys
- list_global_environment_variables, create_global_environment_variable, update_global_environment_variable, delete_global_environment_variable — account-wide variables, with locking and build-pipeline availability
- list_global_config_files, get_global_config_file, create_global_config_file, update_global_config_file, delete_global_config_file — config file templates shared across projects
Requirements
A DeployHQ account. The published server definition takes DEPLOYHQ_EMAIL, DEPLOYHQ_API_KEY and DEPLOYHQ_ACCOUNT — the account name from your DeployHQ URL — with LOG_LEVEL optional. Installed from npm as deployhq-mcp-server and run over stdio with npx, so there is nothing to install first. SSE and HTTP transports are available for hosting it.
Setup effort
One command plus a key — npx -y deployhq-mcp-server, then supply credentials
USE CASES
01
Shipping a change
Find the project and its servers, then deploy the commit range to the right target.
02
Working out why a deploy failed
Find the deployment and read its complete log.
03
Trying it before doing it
Create the deployment in preview mode to see what it would change.
04
Rotating a shared secret
Find the global environment variable, update its value, and lock it against further changes.
05
Standardising a config file across projects
Read the template, edit its body, and update it once for everything that uses it.
06
Setting up access to a new server
Create an SSH key pair for the account and list the fingerprints to confirm it.
18 tools
Listed in project docs. Your client may show a different list.
get_projectlist_serverslist_deploymentsget_deploymentget_deployment_logcreate_deploymentlist_ssh_keyscreate_ssh_keylist_global_environment_variablescreate_global_environment_variableupdate_global_environment_variabledelete_global_environment_variablelist_global_config_filesget_global_config_filecreate_global_config_fileupdate_global_config_filedelete_global_config_fileBEFORE YOU INSTALL
What to know first
Tools you get
18 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js 18+
- DEPLOYHQ_API_KEY in your environment
- DEPLOYHQ_ACCOUNT in your environment
- DEPLOYHQ_EMAIL in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y deployhq-mcp-serverMCP Clients
Claude Code, Claude Desktop
JSON
{
"mcpServers": {
"deployhq": {
"command": "npx",
"args": [
"-y",
"deployhq-mcp-server"
],
"env": {
"DEPLOYHQ_EMAIL": "<YOUR_DEPLOYHQ_EMAIL>",
"DEPLOYHQ_API_KEY": "<YOUR_DEPLOYHQ_API_KEY>",
"DEPLOYHQ_ACCOUNT": "<YOUR_DEPLOYHQ_ACCOUNT>"
}
}
}
}
