LogsLoom
Server Details
Ingest and search LogsLoom logs from coding agents.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool has a clear operational role: single-fetch, batch ingest, project-scope check, and filtered search. The only minor ambiguity is that logs_projects_list and logs_search both mention GET /v1/logs, but their intents are distinct enough for an agent to choose correctly.
Three tools follow a clear logs_<verb> pattern: logs_get, logs_ingest, logs_search. logs_projects_list deviates because the verb comes after the noun, breaking the otherwise consistent convention, but the overall pattern remains readable.
Four tools is well-scoped for a focused log ingestion and retrieval server. Each tool covers a necessary operation without redundancy or bloat.
The core lifecycle is covered: ingest events, search logs, and fetch a single log, plus a project-scope/connectivity check. Some capabilities like log deletion or explicit project listing are absent, but logs are typically append-only and those gaps are consistent with the API's apparent design.
Available Tools
4 toolslogs_getGet a log by idAInspect
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.
Inputs: id (required).
logs_ingestIngest logsAInspect
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).
Inputs: level, events, message, service, +3 more.
logs_projects_listCurrent project scopeAInspect
There is no user-session projects API. Returns the project scope implied by the current API key (connectivity check via GET /v1/logs).
Inputs: no named parameters.
logs_searchSearch logsBInspect
List logs for the API-key's project (GET /v1/logs). Filters: q (message contains), level, service, limit, offset.
Inputs: q, level, limit, offset, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Errors, traces, replays and logs from Talaria for coding agents.
Query your app's logs, metrics and incidents from your AI assistant.
Production observability for AI agents: search runs, read evaluations, acknowledge incidents.
Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceIndexes and searches agent conversation logs from Antigravity and Cursor workspaces, enabling semantic search, token analysis, and benchmarking over local SQLite storage.19 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables semantic search over local AI-agent session logs (e.g., Claude Code, Hermes) using local embeddings, returning relevant chunks without exposing full transcripts.MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to search locally indexed past sessions from Claude Code, Codex CLI, Pi, and custom JSONL logs with citations, while redacting secrets before storage.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables searching, indexing, and recovering past AI chat sessions and agent actions from local AI coding tools, with optional vector database semantic search and direct filesystem access.-
Glama MCP Gateway
Add one secure layer between your agents and this server.