LogsLoom MCP Server

by efim23 Your server? Claim it

answering

LogsLoom is answering right now. Last checked 3 min ago. 274 installs a week from npm. It exposes 4 tools.

Ingest and search LogsLoom logs from coding agents.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 230 · avg 9

a month agotoday

Uptime history 18 hours of history

18 hours agonow

100.0%

Uptime 24h

65 of 65 checks

Tools

read from the server

204 ms

Response time

average over 24h

274

Installs / week

npm and PyPI

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add logsloom --transport http https://mcp.logsloom.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "logsloom": {
      "url": "https://mcp.logsloom.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.logsloom]
url = "https://mcp.logsloom.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "logsloom": {
      "url": "https://mcp.logsloom.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "logsloom": {
      "url": "https://mcp.logsloom.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: LOGSLOOM_API_KEY (Project API key (lb_live_…). Required for stdio.), LOGSLOOM_API_URL (LogsLoom HTTP API origin.). The author declared them in the registry entry; get the values from the project itself.

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

logs

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.logsloom.com/mcp	streamable-http	answering	124 ms	3 min ago

Alternatives to LogsLoom

same job, measured the same way

Downtester Status

by downtester

Live service status, active incidents, search, and outage history from Downtester.

answering

Logclaw MCP Server

by robeldev

Connect AI coding tools to LogClaw incidents, logs, and anomaly detections.

37 installs/wk local only

Graylog MCP Server

by jperelli

Query logs from Graylog: get streams, search messages, aggregate, and get full data.

62 installs/wk local only

Web

by rog0x

Web scraping, search, monitoring, and HTML-to-markdown for AI agents

32 installs/wk local only

Claude Code Usage

by wheelbarrel00

Claude Code token usage, cost, and plan limits from local logs and Anthropic's usage API.

28 installs/wk local only

redline

by gowtham0992

Run local prompt regression checks from prompt-response logs in AI coding assistants.

56 installs/wk local only

AppContext

by appcontext

Live iOS Simulator and browser screenshots, logs, and a personal MCP hub for AI coding agents.

41 installs/wk local only

Devloop

by vincentvella

Browser + dev-server logs on one correlated timeline, for Claude Code and AI agents.

97 installs/wk local only

LogsLoom — questions

Answers built from our own checks of this server.

What can LogsLoom do?

It exposes 4 tools, read directly from the server on our last check. Among them: logs_get, logs_ingest, logs_projects_list, logs_search. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is LogsLoom working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 65 of 65 checks got a reply (100.0%), average response time 204 ms. The bar chart above shows every period we have measured.

Is LogsLoom still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect LogsLoom?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does LogsLoom need an API key?

No. LogsLoom completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is LogsLoom?

It answers our handshake in 204 ms on average, which is faster than 65% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use LogsLoom?

The npm package @logsloom/mcp was installed 274 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.