Back to Browse

Opsmaxx MCP Server

Developer ToolsModerate7.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

7.2
Moderate7.2Low Risk

This is a well-designed protocol relay with appropriate authentication and minimal attack surface. The server forwards MCP messages unmodified between stdio and authenticated HTTP, with proper token handling via environment variables or cached CLI sessions. No malicious patterns, code injection risks, or data exfiltration detected. Minor code quality observations around error handling breadth do not materially affect security. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

7 files analyzed · 5 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

What You'll Need

Set these up before or after installing:

Session token from AI & MCP -> AI Agents -> New AI agent session in the OpsMaxx app. Scoped to one workspace and one access group.Required

Environment variable: OPSMAXX_MCP_TOKEN

Port the OpsMaxx MCP bridge listens on, shown under AI & MCP -> Security. Defaults to the session cached by the opsmaxx CLI.Optional

Environment variable: OPSMAXX_MCP_PORT

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-opsmaxx-opsmaxx": {
      "env": {
        "OPSMAXX_MCP_PORT": "your-opsmaxx-mcp-port-here",
        "OPSMAXX_MCP_TOKEN": "your-opsmaxx-mcp-token-here"
      },
      "args": [
        "-y",
        "@opsmaxx/mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

@opsmaxx/mcp

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

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:

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

{
  "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

Reviews

No reviews yet

Be the first to review this server!