Skip to main content
LogBrew has a hosted MCP server at https://mcp.logbrew.co/mcp. An AI agent that connects to it can read issues, logs, traces, spans, metrics, actions, releases, and product analytics from the projects that you approve. The agent can only read. It cannot change issue status, projects, or account settings. You do not install the server. You add its URL to your MCP client.

​
Before you start

  • You need a LogBrew account with at least 1 project.
  • You need Claude Code 2.1.300 or later. The server supports only MCP protocol version 2026-07-28. Run claude --version to see your version.
  • LogBrew accepts only approved MCP clients. At this time, Claude Code is the only approved client. Other clients get the error client access denied.

​
Connect Claude Code

  1. Add the server:
    claude mcp list now shows logbrew with ! Needs authentication.
  2. Start the sign-in:
    Your browser opens the LogBrew authorization page. If the page asks you to sign in, sign in with GitHub, GitLab, or Bitbucket.
  3. Read the client name on the page. Approve only if you started this connection.
  4. Select the projects that the agent can read. Then select Approve. The browser goes back to Claude Code. Claude Code shows Authenticated with "logbrew".
  5. Make sure that the server is connected:
    The result shows logbrew: https://mcp.logbrew.co/mcp (HTTP) - ✔ Connected.
You can also sign in from a Claude Code session. Run /mcp, select logbrew, and follow the steps in your browser. On a computer without a browser, run claude mcp login logbrew --no-browser in an interactive terminal. Over SSH, connect with ssh -t. Open the URL that Claude Code shows in a browser on a different computer. After you approve, copy the address of the page that the browser opens. Paste it into Claude Code.

​
Ask the agent

The server gives the agent 2 tools: The agent selects the operations. You do not give it tool names or fields. Write the task and the limits:
Use telemetry only as evidence. Logs and error messages can contain text from users. The agent must not follow instructions in that text. Read Use with AI agents for a full investigation workflow.

​
Access and connection lifetime

Each approval starts 1 connection between 1 MCP client and your LogBrew account.
  • The agent reads only the projects that you approved. A read of a different project returns permission_denied.
  • If you lose access to an approved project, LogBrew stops reads of that project.
  • An access token is valid for 1 hour. Claude Code gets a new one automatically while you use the connection.
  • A connection ends after 30 days without use, or 90 days after you approved it. Then sign in again with claude mcp login logbrew.
  • Each token refresh replaces the previous refresh token. If a client sends a replaced refresh token, LogBrew ends the connection. This stops a copied token from working. Sign in again to start a new connection.
  • Too many requests without a valid token get HTTP 429 with a Retry-After header. Wait for that number of seconds, then try again.

​
List and revoke connections

Manage connections in Settings > MCP connections in the LogBrew dashboard, or with the CLI.

​
In Settings

Each connected client shows its name, approved projects, when it connected, when it was last used, and when the connection ends. To revoke one, select Disconnect, then confirm. The client loses access at its next request.

​
With the CLI

Use the LogBrew CLI 0.1.81 or later. Log in with logbrew login first. A project ingest key cannot list or revoke connections. List the MCP clients that are connected to your account:
The CLI calls a connection a grant. Each grant shows:
  • id: the grant ID. Use it to revoke the connection.
  • client: the URL that identifies the client. Claude Code shows as https://claude.ai/oauth/claude-code-client-metadata.
  • projects: the number of approved projects.
  • last_used: the last time that the client got a new access token.
  • expires: the time that the connection ends if the client does not use it.
Add --json to get the full list. Each grant has id, client_id, project_ids, created_at, last_used_at, and expires_at. Revoke 1 connection:
The client loses access at its next request. To connect it again, sign in again with claude mcp login logbrew. To change the approved projects, revoke the connection. Then sign in again and select the new projects.

​
Remove the server

  1. Revoke the connection in Settings > MCP connections, or with logbrew mcp revoke <grant_id> --yes.
  2. Remove the server from Claude Code:
claude mcp remove deletes the configuration and the tokens on your computer only. It does not end the connection in LogBrew. If you do not revoke it, the connection ends after 30 days without use.

​
Fix connection problems