bots.st/logsloom
LogsLoom
Fetch, ingest, and search coding-agent logs
2094 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 4
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.logsloom.com/mcpNeeds header Authorization - npm
npx -y @logsloom/mcpReleased 11 Sep 2026, version 0.1.1Set LOGSLOOM_API_KEY
What it can do
| Tool | What it says it does |
|---|---|
logs_get | Fetch one log by id. The HTTP API has no GET /v1/logs/:id yet, so this tries that path and falls back to searching the latest list page. |
logs_ingest | Send one or many log events to LogsLoom (POST /v1/logs). Provide a single event via level+message, or a batch in `events` (max 100). |
logs_projects_list | There is no user-session projects API. Returns the project scope implied by the current API key (connectivity check via GET /v1/logs). |
logs_search | List logs for the API-key's project (GET /v1/logs). Filters: q (message contains), level, service, limit, offset. |
In its maker's words
Ingest and search LogsLoom logs from coding agents.
- Website
- logsloom.com
- Source
- github.com/efim23/logsloom
- Publisher
- efim23
- Listed from
- the official MCP Registry as
io.github.efim23/logsloom - Version
- 0.1.1, updated 17 Sep 2026
- Kinds of work
- Search and research, Data and databases
The domain it lives on
- logsloom.com
- registered 10 Feb 2026 (9 months ago), at Cloudflare, Inc., its name does not resolve now
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2094 ms | |
| Answered | 2978 ms | |
| Answered | 2132 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.