# deployhq-mcp-server [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/deployhq/deployhq-mcp-server  
**GitHub Stars:** 13  
**npm Downloads (last month):** 175  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/deployhq-mcp-server

## Description
Model Context Protocol (MCP) server for DeployHQ API integration

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "deployhq-mcp-server": {
    "command": "npx",
    "args": ["-y","deployhq-mcp-server"],
    "env": {
      "DEPLOYHQ_EMAIL": "",
      "DEPLOYHQ_API_KEY": "",
      "DEPLOYHQ_ACCOUNT": ""
    }
  }
}
```

**Requires environment variables:** `DEPLOYHQ_EMAIL`, `DEPLOYHQ_API_KEY`, `DEPLOYHQ_ACCOUNT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What deployhq-mcp-server MCP server does

deployhq-mcp-server MCP server exposes DeployHQ account and deployment operations to MCP-compatible AI assistants. It covers project discovery, project details, server listing, deployment history, deployment details, and deployment logs. It also provides tools for creating deployments from specified revisions, with options for branches, queue or preview mode, config-file copying, build commands, build caching, and using the latest deployed commit as the starting point.

Account-level operations extend beyond deployments. Assistants can list SSH public keys and create new ED25519 or RSA key pairs. They can also list, create, update, and delete global environment variables, as well as list, inspect, create, update, and delete global config file templates.

## How it works

The package communicates with DeployHQ through MCP tool calls. Its primary transport is stdio, which lets a local MCP client start the process and exchange requests through standard input and output. SSE and HTTP transports are also available as optional choices for hosting scenarios.

Credentials are read from environment variables rather than being stored by the server. TypeScript and Zod are used in the implementation for typed code and input validation, and the project documents error handling and logging as part of its runtime behavior. Deployment listings accept an optional page number and can be filtered by server UUID.

The deployment workflow can combine several tools: an assistant may list a project's deployments, retrieve a specific deployment, and then request its complete log as text. The log tool is intended to help investigate failed deployments. Project and server identifiers are generally represented by permalinks, UUIDs, or other identifiers required by the relevant operation.

## Setup and configuration

The deployhq-mcp-server MCP server can be run directly with npx, so the documented setup does not require a separate package installation. Configure an MCP client to execute `npx -y deployhq-mcp-server` and pass these required environment variables:

- `DEPLOYHQ_EMAIL`: DeployHQ account email.
- `DEPLOYHQ_API_KEY`: DeployHQ API key.
- `DEPLOYHQ_ACCOUNT`: DeployHQ account name or identifier.

`LOG_LEVEL` is optional and defaults to `INFO`; the documented values are `ERROR`, `INFO`, and `DEBUG`.

The README provides configurations for Claude Desktop and Claude Code. Claude Desktop uses its client configuration file, while Claude Code can use a project-level `.claude.json` entry. After changing configuration, restart the relevant client or session. The documented Claude Code command adds the server with stdio transport and passes the three credentials as environment variables.

## Tools and capabilities

The 18 documented tools are grouped by function:

- Projects and servers: list projects, retrieve a project by permalink, and list servers for a project.
- Deployments: list deployments with pagination and optional server filtering, retrieve deployment details, retrieve deployment logs, and create deployments.
- SSH keys: list public keys and create a key pair with ED25519 as the default type or RSA as an option.
- Global environment variables: list masked values and settings, then create, update, or delete variables. Creation and updates support locking and build-pipeline availability.
- Global config files: list templates, retrieve a template including its body, and create, update, or delete templates. Templates support paths, contents, descriptions, and a build-pipeline flag.

Creating a deployment requires a project, a server or server-group identifier, and starting and ending commit revisions. Optional controls determine the branch, deployment mode, configuration-file copying, build-command execution, build-cache use, and latest-commit behavior.

## Limitations and notes

It specifically documents Claude Desktop and Claude Code rather than describing client-specific setup for other applications. SSH key listing returns public key information and does not return private keys. Environment variable listings return masked values, while config-file retrieval includes the template body. Operations that delete global environment variables or config file templates cannot be undone.

_Full upstream README: https://allmcps.com/mcp/deployhq-mcp-server/readme_