Loading
LiveNX Network Observability MCP Server
The publisher's own command. Not a PlugMCP endpoint.
docker run -i --rm quay.io/bluecat/livenxmcp@sha256:c8c17c3428b274be20a5f8f159cc636535018dfff87bd27a72d25cdd8f0a61c3
LIVENXMCP_URL=<value> LIVENXMCP_TOKEN=<secret> MCP_AUTH_MODE=<value> MCP_API_KEY=<secret> MCP_ED25519_PUBLIC_KEY=<value> MCP_SIGNED_KEY_AUDIENCE=<value> MCP_OAUTH_ISSUER=<value> MCP_OAUTH_JWKS_URI=<value> MCP_OAUTH_AUDIENCE=<value> ACCEPT_EULA=<value> claude mcp add com.bluecat-livenxmcp -- docker run -i --rm quay.io/bluecat/livenxmcp@sha256:c8c17c3428b274be20a5f8f159cc636535018dfff87bd27a72d25cdd8f0a61c3
Run in a terminal.
{
"mcpServers": {
"com.bluecat-livenxmcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/livenxmcp@sha256:c8c17c3428b274be20a5f8f159cc636535018dfff87bd27a72d25cdd8f0a61c3"
],
"env": {
"LIVENXMCP_URL": "<value>",
"LIVENXMCP_TOKEN": "<secret>",
"MCP_AUTH_MODE": "<value>",
"MCP_API_KEY": "<secret>",
"MCP_ED25519_PUBLIC_KEY": "<value>",
"MCP_SIGNED_KEY_AUDIENCE": "<value>",
"MCP_OAUTH_ISSUER": "<value>",
"MCP_OAUTH_JWKS_URI": "<value>",
"MCP_OAUTH_AUDIENCE": "<value>",
"ACCEPT_EULA": "<value>"
}
}
}
}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
LiveNX Network Observability MCP Server
README is not crawled yet. No repository on file.
No tool list yet. Remote servers get one after the first health check.