MCP and epure-cli

MCP and epure-cli are two clients for the same backend: Epure’s dashboard HTTP API with a personal access token (PAT). They do not send exceptions — use a Sentry SDK + DSN for ingest: Quickstart.

HTTP reference: Agent API · Authentication · OpenAPI agent.openapi.yaml

What are MCP and epure-cli?

Both read EPURE_URL (your public app URL, same idea as EPURE_PUBLIC_URL in Configuration) and EPURE_TOKEN (epure_pat_…).

What do I need first?

1. A running Epure instance (Installation).
2. Admin or Owner on the workspace.
3. A token from Settings → Agent tokens (/settings/agent): Settings.

Personal access token scopes

Every token includes read:agent (required). Add optional scopes when creating the token in the UI or via POST /api/v1/agent-tokens.

Rate limits (per instance): about 120 reads and 20 writes per minute per client IP and token prefix.

Environment variables

epure-cli also accepts --url and --token instead of env vars.

Install epure-mcp

The package @epure/mcp is not published to npm. Build from the product repo:

cd tools/epure-mcp
npm ci
npm run build

Entrypoint: tools/epure-mcp/dist/index.js (Node 18+).

Configure an MCP client

Add a stdio server to your host’s MCP config. Example shape (paths are absolute on your machine):

{
  "mcpServers": {
    "epure": {
      "command": "node",
      "args": ["/absolute/path/to/epure/tools/epure-mcp/dist/index.js"],
      "env": {
        "EPURE_URL": "http://localhost:8080",
        "EPURE_TOKEN": "epure_pat_…"
      }
    }
  }
}

• Cursor: user or project MCP config (stdio).
• Other hosts: same command / args / env; refer to your host’s MCP documentation.

If EPURE_TOKEN is missing, the server exits before serving tools.

MCP tools

Resource epure://api/catalog — text index of common /api/v1 routes (also embedded in the MCP server). Use epure_api for paths not wrapped as named tools (projects, DSN, webhooks, setup, stats).

Install epure-cli

Inside the Compose app container (binary ships in the GHCR image):

docker compose exec epure epure-cli auth whoami

From source (repo root):

cargo build --release --bin epure-cli
./target/release/epure-cli auth whoami

Set EPURE_URL and EPURE_TOKEN, or pass --url / --token.

epure-cli command cheat sheet

export EPURE_URL=https://errors.example.com
export EPURE_TOKEN=epure_pat_…

# Prioritized queue (table output)
epure-cli --output table queue --limit 20
epure-cli queue --project PROJECT_UUID --env production

# Fix context (markdown to stdout or file)
epure-cli context ISSUE_UUID --format markdown
epure-cli context ISSUE_UUID --format markdown --out /tmp/fix.md

# Issue summary
epure-cli issue show ISSUE_UUID

# Triage (needs write:triage on token)
epure-cli triage resolve ISSUE_UUID --release my-app@1.2.0
epure-cli triage ignore ISSUE_UUID
epure-cli triage reopen ISSUE_UUID
epure-cli triage snooze ISSUE_UUID --mode hours

# Alerts
epure-cli alerts --view unread --limit 50

# Token identity
epure-cli auth whoami

# Any dashboard route
epure-cli api GET '/api/v1/projects'
epure-cli api PATCH '/api/v1/issues/ISSUE_UUID' --body '{"status":"resolved"}'

Global flag --output: json (default) or table (queue only).

Suggested workflow

1. epure_queue or epure-cli queue — pick an issue.
2. epure_issue_context or epure-cli context … --format markdown — same class of output as ⌘⇧C in the UI: Issues.
3. Patch your application repo; run tests.
4. epure_triage_resolve or epure-cli triage resolve — only after you confirm the fix (do not auto-resolve in unattended loops without policy).

Admin tasks (new DSN, webhook): use epure_api or epure-cli api with a token that includes write:admin.

Not for ingest

PATs and MCP never replace the DSN. Browser and server exceptions still use the official Sentry SDK: Pick your SDK.

FAQ

Next