Relays MCP commands from stdio clients to a running OpsMaxx desktop app to manage SSH, files, containers, and databases.
Also known as OpsMaxx/opsmaxx-mcp, opsmaxx-mcp, @opsmaxx/mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.3
- Last commit
- Sep 13, 2026
- License
- —
What is OpsMaxx MCP?
OpsMaxx relays MCP commands from stdio clients to a running OpsMaxx desktop app to manage SSH, files, containers, and databases.
Summary generated from the project's README
About OpsMaxx MCP server
This adapter functions as a protocol relay that connects stdio-based MCP clients to a running OpsMaxx desktop application. It is specifically designed for clients like Claude Desktop that cannot natively communicate with HTTP-based MCP servers via URLs or custom headers. By acting as a bridge, it forwards messages unmodified between the client and the local desktop app, ensuring that all security policies, access groups, and audit logs managed by OpsMaxx remain intact.
To use this server, you must have the OpsMaxx desktop app running with the bridge enabled under the AI & MCP settings. Users can configure the connection using environment variables such as OPSMAXX_MCP_TOKEN, OPSMAXX_MCP_PORT, or OPSMAXX_MCP_URL. If you have previously used the opsmaxx CLI, the server can automatically read your cached session. This setup allows an AI agent to manage SSH connections, files, containers, and databases through the existing OpsMaxx infrastructure without exposing sensitive credentials like private keys or database passwords directly to the agent.
What you can do with it
- 1Connect Claude Desktop to OpsMaxxConfigure Claude Desktop to interact with your local OpsMaxx instance by using the npx command and required environment variables.
- 2Maintain strict security boundariesEnsure that AI agents can perform tasks without ever receiving direct access to SSH passwords or private keys.
Written from the project's README. Every use case is checked against a quote from it.
How to install OpsMaxx MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall OpsMaxx MCP in Claude Code
$ claude mcp add --env 'OPSMAXX_MCP_TOKEN=<YOUR_OPSMAXX_MCP_TOKEN>' opsmaxx-mcp -- npx -y @opsmaxx/mcpInstall OpsMaxx MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"opsmaxx-mcp": {
"command": "npx",
"args": [
"-y",
"@opsmaxx/mcp"
],
"env": {
"OPSMAXX_MCP_TOKEN": "<YOUR_OPSMAXX_MCP_TOKEN>"
}
}
}
}Install OpsMaxx MCP in VS Code
.vscode/mcp.json
{
"servers": {
"opsmaxx-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@opsmaxx/mcp"
],
"env": {
"OPSMAXX_MCP_TOKEN": "<YOUR_OPSMAXX_MCP_TOKEN>"
}
}
}
}Install OpsMaxx MCP in VS Code CLI
$ code --add-mcp '{"name":"opsmaxx-mcp","type":"stdio","command":"npx","args":["-y","@opsmaxx/mcp"],"env":{"OPSMAXX_MCP_TOKEN":"<YOUR_OPSMAXX_MCP_TOKEN>"}}'Install OpsMaxx MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"opsmaxx-mcp": {
"command": "npx",
"args": [
"-y",
"@opsmaxx/mcp"
],
"env": {
"OPSMAXX_MCP_TOKEN": "<YOUR_OPSMAXX_MCP_TOKEN>"
}
}
}
}Install OpsMaxx MCP in Codex
$ codex mcp add opsmaxx-mcp --env 'OPSMAXX_MCP_TOKEN=<YOUR_OPSMAXX_MCP_TOKEN>' -- npx -y @opsmaxx/mcpInstall OpsMaxx MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.opsmaxx-mcp] command = "npx" args = ["-y", "@opsmaxx/mcp"] [mcp_servers.opsmaxx-mcp.env] OPSMAXX_MCP_TOKEN = "<YOUR_OPSMAXX_MCP_TOKEN>"
Install OpsMaxx MCP in Gemini CLI
$ gemini mcp add -s user -e 'OPSMAXX_MCP_TOKEN=<YOUR_OPSMAXX_MCP_TOKEN>' opsmaxx-mcp npx -- -y @opsmaxx/mcpInstall OpsMaxx MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"opsmaxx-mcp": {
"command": "npx",
"args": [
"-y",
"@opsmaxx/mcp"
],
"env": {
"OPSMAXX_MCP_TOKEN": "<YOUR_OPSMAXX_MCP_TOKEN>"
}
}
}
}Configuration
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.
| Name | Description | |
|---|---|---|
| OPSMAXX_MCP_TOKEN | Session token from AI & MCP -> AI Agents -> New AI agent session in the OpsMaxx app. Scoped to one workspace and one access group. | Secret |
| OPSMAXX_MCP_PORT | Port the OpsMaxx MCP bridge listens on, shown under AI & MCP -> Security. Defaults to the session cached by the opsmaxx CLI. |
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachableopsmaxx/opsmaxx-mcp is public and reachablegithub.com/opsmaxx/opsmaxx-mcp ↗Pass
- Package names this repository as its source@opsmaxx/mcp names opsmaxx/opsmaxx-mcp as sourcenpmjs.com/package/@opsmaxx/mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-09-13github.com/opsmaxx/opsmaxx-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @opsmaxx/mcpPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@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:
| Variable | Meaning |
|---|---|
OPSMAXX_MCP_TOKEN |
Session token from AI & MCP → AI Agents → New AI agent session |
OPSMAXX_MCP_PORT |
Bridge port, shown under AI & MCP → Security |
OPSMAXX_MCP_URL |
Full 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
OpsMaxx MCP questions
How do I add OpsMaxx MCP to Claude Code?
Run claude mcp add --env 'OPSMAXX_MCP_TOKEN=<YOUR_OPSMAXX_MCP_TOKEN>' opsmaxx-mcp -- npx -y @opsmaxx/mcp in your terminal. Add --scope user to make it available in every project.
How do I add OpsMaxx MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What does this server actually do?
It acts as a protocol relay that forwards messages unmodified between a stdio MCP client and the OpsMaxx desktop app.
Do I need to provide a token manually?
No, if you run the 'opsmaxx claude' command once, it reads the session cached by the CLI so no token is required.
Is the token a sensitive credential like an SSH key?
No, the token is scoped to a specific workspace and access group, and does not grant access to SSH passwords, private keys, or database credentials.