super-log Cloud
Server Details
Read your team's hosted journal from an AI agent: every machine's streams, in hub order.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 22.7% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- saxonnicholls/super-log
- GitHub Stars
- 1
- Server Listing
- super-log
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 10 tools
Most tools have clearly separate roles: listing streams, tailing logs, searching recent/historical logs, waiting, and interpreting. The only mild overlaps are search_logs vs search_history (both text search, different windows) and hub_status vs list_streams (both health/orientation views), so an agent might occasionally pick the wrong one.
Names are mostly verb_noun and all snake_case: list_streams, search_logs, tail_logs, wait_for. The deviations are noun compounds like hub_status and stream_guide and a bare verb like interpret, but they are still descriptive and predictable.
Ten tools is a well-sized surface for a log observability platform: orientation, search, tail, wait, analysis, and health are each covered by one or two focused tools. No tool feels redundant or unnecessary.
The set covers the core investigation workflow: check ingestion health, list streams, tail or search current logs, search history, wait for events, and get an interpretation. The main limitation is that it is read-only for webhooks and streams—no tools create or modify them—but that appears consistent with the board-style purpose.
Publisher details
- Operator
- Basseterre LLC · Publisher source
- Operator website
- https://super-log.com
- Vendor relationship
- First-party · Publisher source
- Documentation
- https://super-log.com/#agents
- Privacy policy
- Not provided
- Trust center
- Not available
- Restrictions
- Requires a super-log Cloud account; the free plan includes two seats and the hosted MCP endpoint is included in every plan rather than sold separately. Authentication is a bearer agent token (sla_…) minted in the console under Tokens → Agent token — not OAuth, and no custom OAuth app, admin approval or paid plan is needed. A token is scoped to one organisation. Nine of the ten tools are read-only; the tenth, agent_report, appends to that organisation's agent.* streams and can write nothing else. No regional restriction. Service hosted in the EU.
Available Tools
10 toolsagent_reportAInspect
Put yourself on the org's AGENTS blotter: who you are, what you are doing, how far along. Over the hosted endpoint this is recorded against your agent token and shown on the console.
Inputs: agent (required), status (required), llm, pct, +2 more.
hub_statusAInspect
Check whether the org's benches are sending and how much has arrived. Call this first when logs seem missing - it distinguishes "the bench is down" from "the app logged nothing".
Inputs: no named parameters.
interpretAInspect
Ask super-log Cloud to READ the bench and tell you what happened, whether it matters, and what to do next - the same reading the console shows. audience technical (default) is for the engineer fixing it; executive is the C-suite reading. Covers the org's recent window across every stream; counts against the org's monthly pool. Waits up to wait_ms for the answer and says so if it is still being produced.
Inputs: force, wait_ms, audience.
list_streamsAInspect
Summarise which log streams (topics) are active and their level mix. Cheap orientation - call this before tail_logs so you know what topics exist and where the errors are, instead of guessing topic names.
Inputs: window.
list_webhooksAInspect
The org's inbound webhook endpoints and what last arrived on each - the WEBHOOKS board.
Inputs: no named parameters.
search_historyAInspect
Search the cloud journal: hours or days of history, up to a week. This is the tool for "what happened at 3am" - tail_logs and search_logs only see the last hour.
Inputs: level, limit, since, topic, +2 more.
search_logsAInspect
Find events matching text across the last hour - use when you know what the message says (an exception, an order id, a URL) but not which stream it is in.
Inputs: contains (required), level, limit, topic.
stream_guideAInspect
Detailed documentation for a bench capability, before working with an unfamiliar topic: what its events and metrics mean, how to read them, and the gotchas. No arguments lists everything; name one entry or a playbook for the detail.
Inputs: name.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read your Golem fleet's ledger from any MCP client: agents' sessions, live activity, signed record.
Read a project's prompts, logs and agents, and send new work to the agent on your own machines.
A public travel log for AI agents. Read journals and postcards, and post with a bearer token.
Harness improvements agents post and test for each other. Read without a key; join in one call.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables coding agents from different apps and subscriptions to coordinate as one team over Streamable HTTP, sharing goals, atomic task claims, handoffs, and messages, with questions routed to the owner and answered on a live web board. Each agent reads only what is new to it and can block on a wait call instead of polling a shared file.MIT
- AlicenseNot gradedqualityBmaintenanceEnables a fleet of AI agents to connect over MCP to a local-first hub, where they can read time-ordered project feeds, keep session-scoped memory that survives compaction and resume, exchange artifacts, and send finished work or approval requests to a human inbox.MIT
- AlicenseNot gradedqualityCmaintenanceEnables independent, machine-local AI agent nodes to coordinate without a central hub through an event-sourced CRDT, covering task creation and claiming, shared state, threaded messaging with autonomous replies, and presence tracking. Each node keeps its own append-only log, so agents keep working offline and re-converge with peers whenever they're reachable.MIT

roxabi-senseofficial
AlicenseBqualityBmaintenanceLocal workstation attention journal that tracks focus, idle, and agent sessions, exposing timeline data via MCP for AI agents to query current or past activity.5AGPL 3.0
Glama MCP Gateway
Add one secure layer between your agents and this server.