@opsmaxx/mcp
OfficialThis 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.
@opsmaxx/mcp
Connect any stdio MCP client to a running OpsMaxx desktop app.
npx -y @opsmaxx/mcpWhy 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 claudeSome 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.
Related MCP server: Agent Community MCP
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 |
| Session token from AI & MCP → AI Agents → New AI agent session |
| Bridge port, shown under AI & MCP → Security |
| Full endpoint instead of the port, e.g. |
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
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
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Connect AI clients to your Dactic work context through a hosted MCP service.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceBridges STDIO-based MCP clients with SSE-based MCP servers, allowing applications like Claude Desktop to connect to remote MCP servers that use SSE transport.9-
- AlicenseNot gradedqualityDmaintenanceEnables stdio-only MCP clients to connect to Agent Community's hosted Streamable HTTP MCP server for accessing hosted agents and tools.16 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables stdio-only MCP clients to access Orla's remote Streamable HTTP MCP server by relaying JSON-RPC and managing the OAuth session.209 npmMIT

@asyntai/mcpofficial
AlicenseBqualityBmaintenanceEnables local MCP clients to access the hosted Asyntai MCP server by bridging stdio to HTTPS and handling OAuth sign-in, giving assistants the same 52 tools as the Asyntai dashboard.5459 npm1MIT