Log inSubmit server
Deployhq MCP Server logo

Deployhq MCP Server

Connects AI assistants to DeployHQ for deployment management, project inspection, logs, SSH keys, variables, and config files.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Deployhq MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "deployhq-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "deployhq-mcp-server"
      ],
      "env": {
        "DEPLOYHQ_EMAIL": "YOUR_VALUE_HERE",
        "DEPLOYHQ_API_KEY": "YOUR_VALUE_HERE",
        "DEPLOYHQ_ACCOUNT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y deployhq-mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 3d ago.

Overview

The deployhq-mcp-server MCP server connects AI assistants to the DeployHQ API through project, server, deployment, SSH key, environment variable, and config file tools. It runs primarily over stdio and can be launched with npx, using DeployHQ credentials supplied through environment variables. Reach for it when an assistant needs to inspect deployment state, read logs, create deployments, or manage account-level deployment configuration. Claude Desktop and Claude Code are documented clients.

Use cases

  • Inspect DeployHQ projects and configured servers
  • Check deployment status and retrieve deployment logs
  • Create deployments from selected revisions
  • Manage global environment variables
  • Maintain global config file templates and SSH keys

Key features

  • 18 DeployHQ API tools
  • Project, server, and deployment operations
  • Deployment log retrieval
  • Global environment variable management
  • Global config file template management
  • stdio, SSE, and HTTP transports

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 47d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · deployhq-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars13Stargazers on the source repository.
npm downloads175Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.

How Deployhq MCP Server works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Deployhq MCP Server

deployhq-mcp-server is an MCP server that connects AI assistants to the DeployHQ API. Its main tools list projects and servers, inspect deployments and logs, create deployments, manage SSH keys, and create, update, list, or delete global environment variables and config file templates. It runs primarily over stdio.

Run it with npx using `npx -y deployhq-mcp-server`, so a separate package installation is not required. Add the command to your MCP client configuration and provide `DEPLOYHQ_EMAIL`, `DEPLOYHQ_API_KEY`, and `DEPLOYHQ_ACCOUNT` as environment variables.

It requires `DEPLOYHQ_EMAIL`, `DEPLOYHQ_API_KEY`, and `DEPLOYHQ_ACCOUNT`. These credentials are supplied through environment variables. `LOG_LEVEL` is optional, defaults to `INFO`, and accepts `ERROR`, `INFO`, or `DEBUG`.

Yes, it works with Claude Desktop and Claude Code over stdio. Claude Desktop uses its MCP configuration file, while Claude Code can use a project `.claude.json` configuration or the documented `claude mcp add` command. Restart the client or session after changing configuration.

Yes, it can create deployments. The tool requires a project, a server or server-group identifier, and starting and ending revisions. Optional parameters include branch, queue or preview mode, config-file copying, build commands, build cache, and latest-commit behavior.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDeployhq MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/deployhq-mcp-server?style=directory)](https://allmcps.com/mcp/deployhq-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/deployhq-mcp-server"><img src="https://allmcps.com/api/badge/deployhq-mcp-server?style=directory" alt="Deployhq MCP Server on AllMCPs" /></a>