Opsmaxx

io.github.OpsMaxxPublished by GitHub account OpsMaxxv0.1.3Updated Oct 25, 2026

SSH, files, containers and databases via the OpsMaxx desktop app - scoped per capability, audited.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

A local stdio adapter that relays an MCP client to the running OpsMaxx desktop app, giving scoped, audited access to SSH, files, containers and databases.

What you can do
Relay MCP messages between a stdio client and the OpsMaxx desktop app over authenticated local HTTP, forwarding every message unmodified in both directions, so the client gets the same tools and policy treatment as an HTTP client. Reach SSH hosts, files, containers and databases through the app, scoped per capability and audited. Rely on the app for access groups, approvals, secret redaction and the audit log rather than the adapter. Configure the connection by environment variable or by the session the opsmaxx CLI has already cached.
When to use it
Use it when your MCP client cannot express an HTTP MCP server with an Authorization header, such as Claude Desktop, and you want that client to work with a running OpsMaxx desktop app. Clients that support HTTP servers directly should connect to OpsMaxx without this adapter.
Requirements
A running OpsMaxx desktop app with the bridge enabled under AI & MCP, on the same machine; the adapter talks only to 127.0.0.1. Node.js to run the npm package. A session token in OPSMAXX_MCP_TOKEN, or a session already cached by the opsmaxx CLI; OPSMAXX_MCP_PORT or OPSMAXX_MCP_URL may be set instead of relying on the cache. Desktop only.
Before you install
OPSMAXX_MCP_TOKEN is a secret scoped to one workspace and one access group; keep it out of shared configs. The adapter itself holds no state and cannot exceed what OpsMaxx already allows, but the tools it exposes can act on SSH hosts, files, containers and databases, so writes and changes are possible within the token's scope and are audited in the app. It does not hand the agent SSH passwords, private keys, database credentials or root shells.

Installation

In SourceWeft

  1. Open Opsmaxx in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@opsmaxx/mcp

Connect any stdio MCP client to a running OpsMaxx desktop app.

bash
npx -y @opsmaxx/mcp

Why this exists

OpsMaxx already exposes an MCP server over Streamable HTTP on 127.0.0.1, and clients that can express an HTTP server with an Authorization header — Claude Code, Codex — should use that directly. It is one command:

bash
opsmaxx claude

Some clients cannot. Claude Desktop, notably, does not read url or headers from claude_desktop_config.json at all, so an HTTP MCP server is simply not expressible there. This package is the adapter for those: stdio in, authenticated HTTP out.

What it does, and does not

It is a protocol relay. Every message is forwarded unmodified in both directions. No tool, session or policy logic lives here — access groups, approvals, secret redaction and the audit log all stay in the app, so a stdio client gets exactly the same treatment an HTTP client would.

It talks only to 127.0.0.1. It is not a server, it holds no state, and it cannot reach anything OpsMaxx would not already allow.

OpsMaxx must be running, with the bridge enabled under AI & MCP.

Configuration

Environment first, then the session the opsmaxx CLI has already cached:

VariableMeaning
OPSMAXX_MCP_TOKENSession token from AI & MCP → AI Agents → New AI agent session
OPSMAXX_MCP_PORTBridge port, shown under AI & MCP → Security
OPSMAXX_MCP_URLFull endpoint instead of the port, e.g. http://127.0.0.1:5177/mcp

If none are set it reads the session cached by the CLI, so running opsmaxx claude once is enough and there is no token to paste.

Claude Desktop

json
{  "mcpServers": {    "opsmaxx": {      "command": "npx",      "args": ["-y", "@opsmaxx/mcp"],      "env": {        "OPSMAXX_MCP_TOKEN": "your-session-token",        "OPSMAXX_MCP_PORT": "5177"      }    }  }}

Restart Claude Desktop afterwards.

A note on the token

The token is scoped to one workspace and one access group, and it is the same secret you would otherwise paste into a client's config by hand. It is not an SSH key and it is not a vault password: an agent holding it still never receives an SSH password, a private key, a database credential, a hostname or an interactive root shell. See the threat model.

Licence

MIT. Source: https://github.com/OpsMaxx/OpsMaxx

Source: README.md at commit 7a0c062

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.