com.bluecat/livenxmcp
LiveNX Network Observability MCP Server
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
quay.io/bluecat/livenxmcp@sha256:c8c17c3428b274be20a5f8f159cc636535018dfff87bd27a72d25cdd8f0a61c3claude mcp add livenxmcp -e 'LIVENXMCP_URL=<LIVENXMCP_URL>' -e 'LIVENXMCP_TOKEN=<your livenxmcp_token>' -e 'MCP_AUTH_MODE=<MCP_AUTH_MODE>' -e 'MCP_API_KEY=<your mcp_api_key>' -e 'MCP_ED25519_PUBLIC_KEY=<MCP_ED25519_PUBLIC_KEY>' -e 'MCP_SIGNED_KEY_AUDIENCE=<MCP_SIGNED_KEY_AUDIENCE>' -e 'MCP_OAUTH_ISSUER=<MCP_OAUTH_ISSUER>' -e 'MCP_OAUTH_JWKS_URI=<MCP_OAUTH_JWKS_URI>' -e 'MCP_OAUTH_AUDIENCE=<MCP_OAUTH_AUDIENCE>' -e 'ACCEPT_EULA=<ACCEPT_EULA>' -- docker run -i --rm quay.io/bluecat/livenxmcp@sha256:c8c17c3428b274be20a5f8f159cc636535018dfff87bd27a72d25cdd8f0a61c3
{
"mcpServers": {
"livenxmcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/livenxmcp@sha256:c8c17c3428b274be20a5f8f159cc636535018dfff87bd27a72d25cdd8f0a61c3"
],
"env": {
"LIVENXMCP_URL": "<LIVENXMCP_URL>",
"LIVENXMCP_TOKEN": "<your livenxmcp_token>",
"MCP_AUTH_MODE": "<MCP_AUTH_MODE>",
"MCP_API_KEY": "<your mcp_api_key>",
"MCP_ED25519_PUBLIC_KEY": "<MCP_ED25519_PUBLIC_KEY>",
"MCP_SIGNED_KEY_AUDIENCE": "<MCP_SIGNED_KEY_AUDIENCE>",
"MCP_OAUTH_ISSUER": "<MCP_OAUTH_ISSUER>",
"MCP_OAUTH_JWKS_URI": "<MCP_OAUTH_JWKS_URI>",
"MCP_OAUTH_AUDIENCE": "<MCP_OAUTH_AUDIENCE>",
"ACCEPT_EULA": "<ACCEPT_EULA>"
}
}
}
}
Variables d'environnement
LIVENXMCP_URLobligatoire LiveNX base URL (e.g., https://nxapi.example.com).LIVENXMCP_TOKENobligatoire secret LiveNX API Bearer token.MCP_AUTH_MODEobligatoire Client authentication mode for the /mcp endpoint. One of: none | static-key | signed-key | resource-server. Required at runtime — the server refuses to start without it (no default).MCP_API_KEYsecret Static bearer token clients present as `Authorization: Bearer <key>`. Required only when MCP_AUTH_MODE=static-key.MCP_ED25519_PUBLIC_KEYEd25519 public key (base64url) that MCP_AUTH_MODE=signed-key verifies license tokens against. DEFAULTS TO A SHARED DEMO KEY, which authenticates a token holder rather than a customer — every BlueCat-issued token for this server verifies against it. For anything beyond a trial, generate a per-deployment key pair (license-keygen --gen-key) and set this to its public half.MCP_SIGNED_KEY_AUDIENCEWhen set, a license token must carry exactly this audience or it is rejected — a declarative scope check on top of the key, so a token minted for another deployment fails even if it verifies. Unset means the aud claim is not checked. Only meaningful with MCP_AUTH_MODE=signed-key.MCP_OAUTH_ISSUERToken issuer URL, matched against the iss claim of incoming JWTs. Required when MCP_AUTH_MODE=resource-server — the server refuses to start in that mode without it.MCP_OAUTH_JWKS_URIJWKS endpoint whose public keys verify the signature on every incoming Bearer JWT. Required when MCP_AUTH_MODE=resource-server — the server refuses to start in that mode without it.MCP_OAUTH_AUDIENCEExpected JWT aud claim for MCP_AUTH_MODE=resource-server. A token carrying a different audience, or no aud claim at all, is rejected. Unset skips audience validation entirely.ACCEPT_EULAobligatoire Set to Y (or Yes/YES, any casing) to accept the BlueCat End User License Agreement. The container refuses to start without it.
Questions fréquentes
Qu'est-ce que com.bluecat/livenxmcp ?
LiveNX Network Observability MCP Server
Comment installer com.bluecat/livenxmcp ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add livenxmcp -e 'LIVENXMCP_URL=<LIVENXMCP_URL>' -e 'LIVENXMCP_TOKEN=<your livenxmcp_token>' -e 'MCP_AUTH_MODE=<MCP_AUTH_MODE>' -e 'MCP_API_KEY=<your mcp_api_key>' -e 'MCP_ED25519_PUBLIC_KEY=<MCP_ED25519_PUBLIC_KEY>' -e 'MCP_SIGNED_KEY_AUDIENCE=<MCP_SIGNED_KEY_AUDIENCE>' -e 'MCP_OAUTH_ISSUER=<MCP_OAUTH_ISSUER>' -e 'MCP_OAUTH_JWKS_URI=<MCP_OAUTH_JWKS_URI>' -e 'MCP_OAUTH_AUDIENCE=<MCP_OAUTH_AUDIENCE>' -e 'ACCEPT_EULA=<ACCEPT_EULA>' -- docker run -i --rm quay.io/bluecat/livenxmcp@sha256:c8c17c3428b274be20a5f8f159cc636535018dfff87bd27a72d25cdd8f0a61c3. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour com.bluecat/livenxmcp ?
Oui. Il attend LIVENXMCP_URL, LIVENXMCP_TOKEN, MCP_AUTH_MODE, MCP_API_KEY, ACCEPT_EULA, à renseigner dans sa configuration.
Qui maintient com.bluecat/livenxmcp ?
Il est publié par com.bluecat. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.