Read your team's hosted journal from an AI agent: every machine's streams, in hub order.
Connect Remote server
claude mcp add --transport http super-log-cloud https://api.super-log.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"super-log-cloud": {
"url": "https://api.super-log.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"super-log-cloud": {
"type": "http",
"url": "https://api.super-log.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.super-log.com/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Bearer <agent token>, minted at app.super-log.com under Tokens - Agent token (MCP). It reads this organisation's cloud journal (the nine tools of the local super-log server, plus interpret - a plain-English reading of what happened, technical or executive) and can write only agent.* ; it can never… |
Details
| Endpoint | https://api.super-log.com/mcp (Streamable HTTP) |
| First published | 19 Sep 2026 |
| Last updated | 19 Sep 2026 |
| Registry name | com.super-log/super-log-cloud |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
