Bugsly for AI agents

With an account: Settings, AI Agent / MCP, Generate Token. Without a browser: one call creates an account, an organization, a project and a 90-day token. Signup is rate limited to 5 requests per minute per IP.

curl -X POST https://bugsly.dev/api/v1/auth/agent-signup \
  -H "Content-Type: application/json" \
  -d '{"name": "my-agent"}'

# Returns: token (bgs_...), expires_at, org_id, project_id, dsn

Bugsly accepts the Sentry envelope format, so a Sentry SDK pointed at the DSN works. @bugsly/node is a thin wrapper around @sentry/node.

npm install @bugsly/node

import * as Bugsly from "@bugsly/node";

Bugsly.init({ dsn: "https://<public_key>@bugsly.dev/<project_id>" });

try {
  await riskyOperation();
} catch (err) {
  Bugsly.captureException(err);
}

Needs Node.js 18.17 or newer. Replace YOUR_BUGSLY_TOKEN with the bgs_ token. In a committed .mcp.json write "${BUGSLY_TOKEN}" and export the variable instead, so the token stays out of git.

# Claude Code
claude mcp add bugsly -e BUGSLY_TOKEN=YOUR_BUGSLY_TOKEN -- npx -y @bugsly/mcp-server

# Cursor: ~/.cursor/mcp.json   Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "bugsly": {
      "command": "npx",
      "args": ["-y", "@bugsly/mcp-server"],
      "env": { "BUGSLY_TOKEN": "YOUR_BUGSLY_TOKEN" }
    }
  }
}

The MCP tools are thin wrappers over these endpoints; the same bearer token works for both.

curl https://bugsly.dev/api/v1/organizations \
  -H "Authorization: Bearer YOUR_BUGSLY_TOKEN"

curl "https://bugsly.dev/api/v1/projects/PROJECT_ID/issues?status=unresolved" \
  -H "Authorization: Bearer YOUR_BUGSLY_TOKEN"

# Revoke a token (id from GET /api/v1/auth/api-tokens)
curl -X DELETE https://bugsly.dev/api/v1/auth/api-tokens/TOKEN_ID \
  -H "Authorization: Bearer YOUR_BUGSLY_TOKEN"