Setup

@loguro/mcp is the Model Context Protocol server for querying Loguro logs directly from Claude Code (or any MCP-aware client).

There is no daemon to manage and no global install required — Claude Code spawns the server on demand via bunx, and a fresh process serves each conversation.

Install

You don’t need to install anything ahead of time. The recommended setup uses bunx, which fetches and runs the latest version on each spawn:

bunx @loguro/mcp

If you prefer a permanent install, the package is on npm:

npm i -g @loguro/mcp

Authenticate

The MCP server needs a Loguro PAT (personal access token). The fastest path is to log in once with the CLI — the MCP picks up the saved token automatically:

loguro login

This writes ~/.config/loguro/auth.json, which the MCP reads on startup. If you don’t have the CLI installed, you can pass LOGURO_TOKEN via the MCP config block instead (see below).

Get a PAT from /app/settings/cli-tokens in the web console.

Connect to Claude Code

Add the server to ~/.claude/settings.json (global) or .claude/settings.json (per project).

With saved CLI auth (recommended):

{
  "mcpServers": {
    "loguro": {
      "command": "bunx",
      "args": ["@loguro/mcp"],
      "env": {
        "LOGURO_PROJECT": "your-project-slug"
      }
    }
  }
}

With explicit token:

{
  "mcpServers": {
    "loguro": {
      "command": "bunx",
      "args": ["@loguro/mcp"],
      "env": {
        "LOGURO_TOKEN": "pat_…",
        "LOGURO_PROJECT": "your-project-slug"
      }
    }
  }
}

LOGURO_PROJECT is optional — if you set it, you can ask Claude things like “show me the last 50 errors” without specifying the project on every tool call.

Verify

Restart Claude Code and ask:

List the distinct log levels in this project.

Claude should call get_distinct_values and return the list. If the server can’t authenticate, it exits immediately with Error: no PAT found. Run loguro login first, or set LOGURO_TOKEN env var. on stderr.