LogBrew MCP Server

by logbrew Your server? Claim it

answering

LogBrew is answering right now. Last checked 6 min ago. Last commit 31 Oct 2026.

Read LogBrew errors, slow traces, logs, and product analytics, and triage issues with consent.

Uptime history 6 days of history · worst day 99%

6 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

209 ms

Response time

average over 24h

Stars

last commit 31 Oct 2026

LogBrew missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.logbrew.co/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.logbrew.co/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.logbrew.co/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.logbrew.co/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.logbrew.co/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.logbrew.co/mcp	streamable-http	sign-in	217 ms	6 min ago

Alternatives to LogBrew

same job, measured the same way

Condux error monitoring

by condux

Read your Condux issues, events and stack traces (deminified with source maps). Triage optional.

answering

Shipbook

by shipbook

Debug production issues using Shipbook logs and Loglytics error insights.

answering

Auralogs

by auralogs

Read-only access to Auralogs production logs: search logs, inspect errors, review AI analyses.

7 tools answering

Talaria

by newtalaria

Errors, traces, replays and logs from Talaria for coding agents.

answering

OnyxMetric

by onyxmetric

Read and manage OnyxMetric web analytics: traffic, errors, funnels, goals, sites and segments.

answering

DebugBundle

by debugbundle

DebugBundle MCP: runtime error reporting, incident response, health checks, and product analytics.

376 installs/wk local only

Chipp Observability

by chipp

Chipp: a deployed project's database (read), logs, errors, analytics, CI status, custom actions.

answering

Ripples Metrics

by ripples

Analytics for founders: traffic, search, ad spend, revenue and retention per product.

answering

LogBrew — questions

Answers built from our own checks of this server.

Why is there no tool list for LogBrew?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is LogBrew working right now?

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

How do I connect LogBrew?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to LogBrew?

No API key is involved. LogBrew answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is LogBrew?

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

Is LogBrew open source?

The code is open source: it is published under the Apache-2.0 licence, written in Rust and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.logbrew.co, which runs on its operator's own terms.