L
MCP serverOfficial registry
Livewiremcp
LiveAction LiveWire MCP Server
by com.bluecatv26.2.2
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Local command
docker run -i --rm quay.io/bluecat/livewiremcp@sha256:c1614cbe6bca212d0287c5fdfafc09b83579b38eb7e5f9b1fc4011902d41d385
Credentials from the publisher
- LIVEWIRE_BASE_URL — LiveWire base URL (e.g., https://livewire.example.com).
- LIVEWIRE_API_KEY — 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 — 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 — 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 — Set to Y (or Yes/YES, any casing) to accept the BlueCat End User License Agreement. The container refuses to start without it.
Provider
Claude Code
LIVEWIRE_BASE_URL=<value> LIVEWIRE_API_KEY=<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-livewiremcp -- docker run -i --rm quay.io/bluecat/livewiremcp@sha256:c1614cbe6bca212d0287c5fdfafc09b83579b38eb7e5f9b1fc4011902d41d385
Run in a terminal.
Claude Desktop
{
"mcpServers": {
"com.bluecat-livewiremcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"quay.io/bluecat/livewiremcp@sha256:c1614cbe6bca212d0287c5fdfafc09b83579b38eb7e5f9b1fc4011902d41d385"
],
"env": {
"LIVEWIRE_BASE_URL": "<value>",
"LIVEWIRE_API_KEY": "<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
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchRelated MCP