Bifrost
Provides tools for operating allowlisted Docker containers on a remote server over SSH: listing all containers (name, image, state, status, allowlisted or not), reading the last N lines of a container's logs within an optional time window, and restarting containers when the write risk level is permitted. All container access is restricted to a configured allowlist and enforced server-side by a forced-command gate.
Provides tools for inspecting an Ubuntu server over SSH, including a system overview (hostname, uptime, load, memory, disk, and running containers). Operations are executed as fixed, validated verbs through a server-side gate so the remote host cannot be used as a general-purpose shell.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Bifrost
Operate an Ubuntu server over SSH through typed, scoped operations, without opening a raw shell and without ever giving an AI agent one. The same binary works as:
a CLI for humans:
bifrost docker logs --container web --tail 50a local MCP server (stdio) for agents:
bifrost mcp(Claude Desktop, Cursor, Claude Code, …)
Status: early (0.x). The API, config format and tool names may change between minor versions.
Why
Giving an agent ssh (or a generic run_command tool) means one hallucination away from
docker system prune -af or rm -rf. Bifrost exposes a small set of intent-named operations
(docker_logs, docker_restart, system_overview, …) with strict schemas, and enforces the
real boundary on the server, so even a misbehaving client cannot do more than the allowlist permits.
Related MCP server: Ubuntu VM Control
Security model
Layer | Where | What it guarantees |
| server | The real boundary. The Bifrost key can only run fixed verbs with validated arguments and a container allowlist. Holds even if someone uses the key outside Bifrost. |
| server | Docker is only reachable through the gate (docker group = root). |
Pinned host key ( | client | No MITM ( |
Per-surface policy ( | client | MCP is |
Zod schemas derived from the config | client | The agent only sees, and can only send, allowlisted containers and bounded numbers. |
Token protocol | client | Shell is never sent: only |
Sanitization + | client | ANSI and secrets stripped; server output marked as data, not instructions (prompt-injection mitigation). |
Write rate limit, timeouts, byte cap, audit log | client | Contains looping agents; trail in |
Getting started
Requires Node.js ≥ 22.18.
Server: follow
remote/install.md.Connect (IP, user and password, saved in a local SQLite store):
bifrost connect --ip 203.0.113.10 --user bifrost # prompts for the password without echoThe first time, it shows the server's host key fingerprint and asks you to compare it with
ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pubrun on the server (or pass--fingerprint SHA256:...). Then it checks the login andbifrost-gate ping. Alternatively, use key auth via~/.config/bifrost/config.json(seeconfig.example.json).Containers / policy (optional): a
config.jsonwith onlycontainers,policyandlimitsis still read; the active connection suppliesserverandauth.Check:
bifrost doctor
Saved connections
Command | What it does |
| Verify, test and save a server; it becomes the active one. Reconnecting to the same host reuses the trusted fingerprint (a changed key is refused). |
| List saved connections ( |
| Switch the active connection. |
| Delete a connection and its password. |
The store lives at ~/.local/share/bifrost/bifrost.db (override with BIFROST_DB), mode 0600.
The password is stored in plain text there: anything that can read your files, including an AI agent with
a terminal, can read it. Avoid --password on the command line (shell history, ps); omit it to be prompted.
With password login, the server must force the gate for that user via ForceCommand
(see remote/install.md), otherwise the password is a full shell.
git clone https://github.com/akanyane/bifrost.git && cd bifrost
npm install && npm run build
node dist/bifrost.js doctor
node dist/bifrost.js system overview
node dist/bifrost.js docker ps
node dist/bifrost.js docker logs --container web --tail 50 --since-minutes 30
node dist/bifrost.js docker restart --container web # write: allowed on the CLI, blocked on MCP by default
node dist/bifrost.js --json docker ps # machine-readable outputConfiguration
Key | Default | Description |
| – / | SSH target. |
| required | Host key fingerprint, |
|
| Pinned host key algorithm, so the fingerprint always refers to the same key. |
|
|
|
|
| Allowlist. Must match |
|
| Highest risk ( |
|
| Highest risk allowed for agents. |
|
| Rate limit for agent write operations. |
|
| Per-command timeout, output cap, concurrent SSH channels. |
When a connection is active (bifrost connect), it overrides server and auth. The config path can be overridden with --config <path> or BIFROST_CONFIG. Log level via BIFROST_LOG (debug, info, warn, error, silent).
Using it as an MCP server
Claude Desktop (claude_desktop_config.json) / Cursor (.cursor/mcp.json):
{
"mcpServers": {
"bifrost": {
"command": "node",
"args": ["/absolute/path/to/bifrost/dist/bifrost.js", "mcp"],
"env": { "SSH_AUTH_SOCK": "/path/to/your/ssh-agent.sock" }
}
}
}GUI apps usually do not inherit SSH_AUTH_SOCK from your shell: pass it explicitly (or use
auth.method: "key" with passphraseEnv). To inspect the server interactively: npm run inspect.
Tools exposed with the default policy:
Tool | Risk | Description |
| read | Hostname, uptime, load, memory, disk, running containers. |
| read | All containers with name, image, state, status and whether they are allowlisted. |
| read | Last N lines (≤ 500) of an allowlisted container, optionally within the last N minutes. |
| write | Hidden from agents unless |
Development
npm run dev -- docker ps # runs the TypeScript directly (Node ≥ 22.18 type stripping)
npm test # node:test, includes the real gate script against a fake docker and injection payloads
npm run typecheck
npm run build # tsup -> dist/bifrost.jsLayout:
src/
bin/bifrost.ts single entry point
core/ ssh (persistent session, host key, bounded runner), config, policy, gate, sanitize, audit, logger
operations/ defineOperation + registry (single source of truth) + execute (policy → validation → rate limit → run → audit)
adapters/cli/ Commander commands generated from the registry
adapters/mcp/ MCP tools generated from the registry
remote/ bifrost-gate.sh + server setup guide
test/Code rules: no TypeScript syntax that emits JS (enum, namespace, parameter properties;
enforced by erasableSyntaxOnly), and nothing outside adapters/cli writes to stdout (a test enforces it).
Adding an operation
Add the verb to
remote/bifrost-gate.sh(validate every argument,execwith an argv array, nevereval) plus a case intest/gate.test.ts.Create
src/operations/<group>/<op>.tswithdefineOperation(explicit verb in the name, an honestrisk, a description that states its limits).Register it in
src/operations/registry.ts. The CLI command and the MCP tool appear automatically.
Releases
Releases are automated with release-please.
Use Conventional Commits (feat:, fix:, docs:, feat!: for breaking changes, …).
On every push to main a Release PR is opened or updated; merging it bumps the version
(package.json and src/version.ts), updates CHANGELOG.md, and publishes a GitHub release.
License
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
Scoped, audited SSH exec, sessions, and SFTP on your saved servers without exposing credentials
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA secure protocol server that allows AI assistants to safely interact with Ubuntu systems through controlled file operations, command execution, package management, and system information retrieval.46MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Ubuntu VMs via SSH, including executing commands, simulating keyboard/mouse input, capturing screenshots, and controlling GUI applications remotely.1-
- AlicenseAqualityBmaintenanceEnables AI assistants to manage remote servers via SSH with agentless command execution, file operations, and service management.9MIT
- AlicenseBqualityDmaintenanceConnects to Ubuntu servers over SSH to manage, maintain, and secure them through natural language conversation.35ISC