Skip to content

LogsLoom

by efim23 · remote · local (npm) · no sign-in to list tools · v0.1.1 · published by GitHub user efim23

Ingest and search LogsLoom logs from coding agents.

Final · 1
CompareRegistry entry

4 tools: 1 do something that can't be undone and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http logsloom https://mcp.logsloom.com/mcp --header 'Authorization: <your-authorization>'

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Can't be undone 1Claude Code: ask
  • logs_ingestSend one or many log events to LogsLoom (POST /v1/logs).No findings

    Why it is in this group

    • The name "logs_ingest" says "log": a word for reading.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    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).
Only reads 3Claude Code: allow
  • logs_getFetch one log by id.No findings

    Why it is in this group

    • The name "logs_get" says "log": a word for reading.
    Description, as the server wrote it
    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_projects_listThere is no user-session projects API.No findings

    Why it is in this group

    • The name "logs_projects_list" says "log": a word for reading.
    Description, as the server wrote it
    There is no user-session projects API. Returns the project scope implied by the current API key (connectivity check via GET /v1/logs).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http logsloom https://mcp.logsloom.com/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__logsloom__logs_search",
      "mcp__logsloom__logs_get",
      "mcp__logsloom__logs_projects_list"
    ],
    "ask": [
      "mcp__logsloom__logs_ingest"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as logsloom. Review it before you use it.