Claude Desktop LogsLoom logs_ingest
How to: Claude Desktop LogsLoom logs_ingest
Add LogsLoom to Claude Desktop
-
01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"logsloom": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.logsloom.com/mcp"
]
}
}
}-
02
Save the file and restart Claude Desktop.
-
03
Ask for something logs_ingest does. Claude Desktop lists the server's tools on connect and calls logs_ingest itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that LogsLoom's identifier in your config matches the one above exactly.
Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs
Set these first
LogsLoom will not start until these are set, so logs_ingest never becomes available.
-
LOGSLOOM_API_KEY -
LOGSLOOM_API_URL
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.