com.bluecat/livewiremcp

Registre officiel Autres

LiveAction LiveWire 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 »).

OCI package quay.io/bluecat/livewiremcp@sha256:c1614cbe6bca212d0287c5fdfafc09b83579b38eb7e5f9b1fc4011902d41d385
Claude Code
claude mcp add livewiremcp -e 'LIVEWIRE_BASE_URL=<LIVEWIRE_BASE_URL>' -e 'LIVEWIRE_API_KEY=<your livewire_api_key>' -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/livewiremcp@sha256:c1614cbe6bca212d0287c5fdfafc09b83579b38eb7e5f9b1fc4011902d41d385
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "livewiremcp": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "quay.io/bluecat/livewiremcp@sha256:c1614cbe6bca212d0287c5fdfafc09b83579b38eb7e5f9b1fc4011902d41d385"
            ],
            "env": {
                "LIVEWIRE_BASE_URL": "<LIVEWIRE_BASE_URL>",
                "LIVEWIRE_API_KEY": "<your livewire_api_key>",
                "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

  • LIVEWIRE_BASE_URL obligatoire LiveWire base URL (e.g., https://livewire.example.com).
  • LIVEWIRE_API_KEY obligatoire secret LiveWire API key. Mint a managed durable token (POST /api/v1/tokens/) rather than a /login session token — see --help for the full procedure.
  • MCP_AUTH_MODE obligatoire 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_KEY secret Static bearer token clients present as `Authorization: Bearer <key>`. Required only when MCP_AUTH_MODE=static-key.
  • MCP_ED25519_PUBLIC_KEY Ed25519 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_AUDIENCE When 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_ISSUER Token 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_URI JWKS 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_AUDIENCE Expected 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_EULA obligatoire 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/livewiremcp ?

LiveAction LiveWire MCP Server

Comment installer com.bluecat/livewiremcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add livewiremcp -e 'LIVEWIRE_BASE_URL=<LIVEWIRE_BASE_URL>' -e 'LIVEWIRE_API_KEY=<your livewire_api_key>' -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/livewiremcp@sha256:c1614cbe6bca212d0287c5fdfafc09b83579b38eb7e5f9b1fc4011902d41d385. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour com.bluecat/livewiremcp ?

Oui. Il attend LIVEWIRE_BASE_URL, LIVEWIRE_API_KEY, MCP_AUTH_MODE, MCP_API_KEY, ACCEPT_EULA, à renseigner dans sa configuration.

Qui maintient com.bluecat/livewiremcp ?

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.