# Super Log MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.super-log%2Fsuper-log
Registry id: `mcp-registry/com.super-log/super-log`
Status: unknown

## Install

```json
{
  "mcpServers": {
    "super-log-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@super-log/mcp"
      ]
    }
  }
}
```

Claude Code:

```sh
claude mcp add super-log-mcp-server -- npx -y @super-log/mcp
```

## Tools (6)

- `hub_status`: Is the bench even running? Distinguishes 'hub is down' from 'the app logged nothing' — the first thing to check when logs seem missing.
- `list_streams`: Cheap orientation: which topics are active, their level mix, which ones have errors. Call before tailing so topic names are known, not guessed.
- `search_history`: Search the on-disk journal - hours or days, not the few minutes the hub holds in memory. The tool for 'what happened at 3am'; tail_logs and search_logs cannot s
- `search_logs`: Find events by text across the recent window when you know the message but not the stream.
- `tail_logs`: Recent events, filtered by topic / level / contains, with a cursor (since) so repeat calls only return what is new.
- `wait_for`: Block until a matching event arrives. Use after triggering an action instead of sleeping and hoping; it starts from now, so it cannot be satisfied by something 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.