LiveAction LiveWire MCP Server
The publisher's own command. Not a PlugMCP endpoint.
docker run -i --rm quay.io/bluecat/livewiremcp@sha256:c1614cbe6bca212d0287c5fdfafc09b83579b38eb7e5f9b1fc4011902d41d385
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.
{
"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
LiveAction LiveWire MCP Server
README is not crawled yet. No repository on file.
No FAQ yet. Enrichment fills this from the README on the next crawl.
No tool list yet. Remote servers get one after the first health check.