mcpField
O
opsmaxx

opsmaxx

Local
opsmaxx.devCloud & Infra0Updated 7w ago
RepositoryVisit website

About opsmaxx

opsmaxx is a protocol relay that connects stdio MCP clients to a running OpsMaxx desktop app, including clients that cannot configure HTTP MCP servers. It forwards messages unchanged while the app retains control of access, approvals, and auditing.

Key features

  1. 01Relay MCP messages between stdio and HTTP
  2. 02Connect to the local OpsMaxx bridge endpoint
  3. 03Reuse app access groups and approval policies
  4. 04Keep secret redaction and audit logs in the app
  5. 05Configure sessions through environment variables or CLI cache

Use cases

  1. 01Connect clients that cannot configure HTTP to OpsMaxx
  2. 02Link Claude Desktop to the local MCP bridge
  3. 03Apply OpsMaxx access groups and approval controls
  4. 04Keep stdio client activity in the app audit log

MCP support

This is a protocol relay, not an MCP server. It connects stdio MCP clients to a running OpsMaxx desktop app by forwarding messages through its local Streamable HTTP bridge; tool logic and policies remain in the app.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "opsmaxx-opsmaxx": {
      "command": "npx",
      "args": [
        "-y",
        "@opsmaxx/mcp"
      ],
      "env": {
        "OPSMAXX_MCP_TOKEN": "<OPSMAXX_MCP_TOKEN>",
        "OPSMAXX_MCP_PORT": "<OPSMAXX_MCP_PORT>"
      }
    }
  }
}
Run commandnpx -y @opsmaxx/mcp
Environment variables to set
OPSMAXX_MCP_TOKENSecretSession token from AI & MCP -> AI Agents -> New AI agent session in the OpsMaxx app. Scoped to one workspace and one access group.
OPSMAXX_MCP_PORTPort the OpsMaxx MCP bridge listens on, shown under AI & MCP -> Security. Defaults to the session cached by the opsmaxx CLI.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@opsmaxx/mcp0.1.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.