@bigloupe/mcp

A Model Context Protocol server that connects Claude (Claude Code or Claude Desktop) to your BigLoupe org.

Give Claude a ticket key or issue id and it pulls the complete context — description, screenshot, and the captured session logs (console, network, errors) — so it can actually understand and help fix the bug, not just guess.

What it does

It runs as a local stdio MCP server and exposes these tools to Claude:

| Tool | What it returns | | --- | --- | | list_projects | All projects in your org (name + id). | | list_tickets | Tickets for a project (filter by status, q). | | get_ticket | A ticket with full context: description, absolute screenshot URL, and the attached session's console/network/error logs. | | list_issues | Aggregated error/issue groups for a project. | | get_issue | An issue with its last stack trace + attached session logs. | | get_session | The grouped logs for a session (console, network with headers/bodies, errors, routes, interactions, forms). | | update_ticket_status | Change a ticket's status (open, triaged, accepted, in_progress, ready_for_review, qa_validation, resolved, closed, reopened). | | comment_on_ticket | Post a comment on a ticket (attributed to the agent). | | update_issue_status | Change an issue's status (unresolved, resolved, ignored). | | comment_on_issue | Post a comment on an issue (attributed to the agent). |

Every result includes both a readable markdown summary and the raw structured data, so the model gets the actual data — not just a pointer to it.

Create a BigLoupe API token

1. Open your BigLoupe Dashboard.
2. Go to Settings → API Tokens.
3. Create a new org-scoped token and copy it.

The token is sent on every request as Authorization: Bearer <token>.

Configuration

The only thing you need to set is your token:

| Env var | Required | Description | | --- | --- | --- | | BIGLOUPE_TOKEN | yes | The org-scoped API token from above. | | BIGLOUPE_API_URL | no | API base URL. Defaults to https://api.bigloupe.com. Override only for self-hosted or non-production instances (the server appends /v1). |

Add it to Claude Code

claude mcp add bigloupe \
  --env BIGLOUPE_TOKEN=blp_your_token_here \
  -- npx -y @bigloupe/mcp

Or add it manually to your .mcp.json / Claude Code config:

{
  "mcpServers": {
    "bigloupe": {
      "command": "npx",
      "args": ["-y", "@bigloupe/mcp"],
      "env": {
        "BIGLOUPE_TOKEN": "blp_your_token_here"
      }
    }
  }
}

Add it to Claude Desktop

Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json) and add:

{
  "mcpServers": {
    "bigloupe": {
      "command": "npx",
      "args": ["-y", "@bigloupe/mcp"],
      "env": {
        "BIGLOUPE_TOKEN": "blp_your_token_here"
      }
    }
  }
}

Restart Claude Desktop and the BigLoupe tools will appear.

Self-hosting? Add "BIGLOUPE_API_URL": "https://api.your-domain.com" to the env block (or pass --env BIGLOUPE_API_URL=... to claude mcp add).

Usage

Once connected, just ask Claude things like:

Look at ticket WEB-128 in BigLoupe and tell me what's going wrong.

Fetch the latest unresolved issues for the checkout project and help me fix the top one.

License

MIT