mcpbeat Sign in

Heliograph MCP Server

by heliograph-io Your server? Claim it
local only

Heliograph runs on your own machine — the client starts it, so there is no endpoint to ping. 72 installs a week from npm. Last commit 3 Oct 2026.

Run commands on a machine you cannot SSH into. Air-gapped, bastion-only, change-controlled.

Installs per day peak 25 · avg 9 · -31% w/w
a month agotoday
72
Installs / week
npm · @dbhq/heliograph
0
Stars
64 open issues
3 Oct 2026
Last commit
5 releases in 90 days
Apache-2.0
License
Shell

What the code does

We read the source, 2 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs a command on install [пакет] package.json:1
postinstall: node bin/install.mjs
Package points at a different repository heliograph-io/heliograph
пакет @dbhq/heliograph ссылается на dbhq-uk/heliograph
const child = spawn(bin, process.argv.slice(2), { stdio: 'inherit' });
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    if s.Statuses, err = readStatuses(filepath.Join(dir, statusesDirName)); err != nil {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add heliograph -- npx -y @dbhq/heliograph
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "heliograph": {
      "command": "npx",
      "args": [
        "-y",
        "@dbhq/heliograph"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.heliograph]
command = "npx"
args = ["-y", "@dbhq/heliograph"]
.cursor/mcp.json
{
  "mcpServers": {
    "heliograph": {
      "command": "npx",
      "args": [
        "-y",
        "@dbhq/heliograph"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "heliograph": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dbhq/heliograph"
      ]
    }
  }
}

Alternatives to Heliograph

same job, measured the same way
Heliograph
by dbhq-uk

Run commands on a machine you cannot SSH into. Air-gapped, bastion-only, change-controlled.

local only
Airlox
by claudezss

Run your coding agent's commands on machines you own: a sandboxed job slot, not an SSH login.

1 026 installs/wk local only
LetKite
by letkite

Run commands and manage files on your own machines. Needs a LetKite account; OAuth sign-in.

answering
Conning
by eranyonai

Run commands on your remote test machines over SSH without the agent ever seeing a secret.

448 installs/wk local only
Gatefile
by cloudcorprecords

Extract a repo's contribution gates into machine-readable contribution-gates.json.

88 installs/wk local only
Local Commander
by localcmd

Give your AI hands on every computer you own. One chat, all your machines — even from your phone.

answering
Sidecrew
by lvlrsajjad

Code changes and unit tests by local MLX models, behind a gate a machine can run.

53 installs/wk local only
GitInProgress
by ysk-abe

Group your AI's changes into focused commit candidates; nothing lands until you approve.

local only

Heliograph — questions

Answers built from our own checks of this server.

Why is there no uptime for Heliograph?
Heliograph runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @dbhq/heliograph was installed 72 times last week.
How do I connect Heliograph?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @dbhq/heliograph straight from npm; nothing to host, nothing to sign up for.
How many people use Heliograph?
The npm package @dbhq/heliograph was installed 72 times in the last week. Week over week that is -31%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Heliograph open source?
Yes — it is published under the Apache-2.0 licence, written in Shell, 0 stars on GitHub and 64 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.