Ingest and search LogsLoom logs from coding agents. Connect the official LogsLoom MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http logsloom https://mcp.logsloom.com/mcpRun in your terminal, then restart Claude Code.
LogsLoom · https://mcp.logsloom.com/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “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).”
“Use “logs_search”: List logs for the API-key's project (GET /v1/logs). Filters: q (message contains), level, service, limit, offset.”
“Use “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.”
“Use “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).”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how LogsLoom holds up.
Operated by LogsLoom (logsloom.com) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If LogsLoom adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose LogsLoom in the gate directory. No sign-in needed.
LogsLoom's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
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_search — List logs for the API-key's project (GET /v1/logs). Filters: q (message contains), level, service, limit, offset.
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_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).
https://mcp.logsloom.com/mcpYes — LogsLoom operates its own remote MCP server at mcp.logsloom.com. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick LogsLoom in the directory. No account or sign-in is needed. From then on, LogsLoom's tools are available in every client you've connected to gate.
No. LogsLoom runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect LogsLoom in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up LogsLoom in: Claude · Claude Code · ChatGPT · Cursor · VS Code