Authentication

The MCP server authenticates with a Loguro PAT (personal access token). There are two ways to provide it.

Get a PAT from /app/settings/cli-tokens in the web console — one token covers every project on your account.

Method A — Reuse the CLI’s saved auth

If you’ve run loguro login, the PAT is already on disk at ~/.config/loguro/auth.json. The MCP server reads the same file on startup, so no extra configuration is needed:

loguro login    # paste a pat_… when prompted

The CLI and the MCP share auth — log in once, use it everywhere. The same token works across all your projects.

If XDG_CONFIG_HOME is set, the MCP looks under $XDG_CONFIG_HOME/loguro/auth.json instead of ~/.config/loguro/auth.json.

Method B — Explicit LOGURO_TOKEN env var

For CI runners, shared agents, or environments where the CLI isn’t installed, set LOGURO_TOKEN directly. The MCP picks it up from process.env:

{
  "mcpServers": {
    "loguro": {
      "command": "bunx",
      "args": ["@loguro/mcp"],
      "env": {
        "LOGURO_TOKEN": "pat_…"
      }
    }
  }
}

Precedence

If both are present, LOGURO_TOKEN wins. The server resolves the token as process.env.LOGURO_TOKEN ?? auth.json, so the env var overrides whatever the CLI saved. This is convenient when you want to test against a different account without running loguro logout.

The same precedence applies to LOGURO_BASE_URL — env var first, then baseUrl from auth.json, then the default https://logu.ro.

Failure mode

If neither source provides a token, the MCP exits immediately on startup with:

Error: no PAT found. Run `loguro login` first, or set LOGURO_TOKEN env var.

Claude Code will surface this as a server-failed-to-start error in the MCP panel.