INDIVIDUAL MCP TOOL

list_issue_reports

List issue reports from the one-tap reporter (public.

busymate.devnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.busymate.dev

No auth detected

Connect to this endpoint to inspect the live schema for list_issue_reports and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

busymate.dev

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.busymate-devtools]
url = "https://mcp.busymate.dev"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "busymate-devtools": {
      "type": "http",
      "url": "https://mcp.busymate.dev"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: busymate-devtools
Remote MCP URL: https://mcp.busymate.dev

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "busymate-devtools": {
      "url": "https://mcp.busymate.dev"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "busymate-devtools": {
      "type": "http",
      "url": "https://mcp.busymate.dev"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "busymate-devtools",
  "transport": "streamable-http",
  "url": "https://mcp.busymate.dev"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

list_breakpoint_events — List HELD (paused) breakpoint exchanges — the READ side of the breakpoint-continue flow (public.
get_device — Get one device row by uuid, name, OR its PAC PORT — the DIRECT resolver for a KNOWN device: when you already hold a device uuid/name (from traffic rows, audit events, another tool's result) or a per-device PAC/proxy endpoint, call this instead of browsing or paging list_devices.
list_devices — List devices, ONE PAGE at a time — YOUR OWN by default (owner-scoped to the calling account: the same reach the dashboard gives you), or the WHOLE fleet with `all:true` (devices:view operators only; re-verified server-side — for a non-operator `all` is rejected, never silently widened).
get_device_status — Get a device's live status: `online` is DERIVED truth (#776 — devices.
get_device_health — THE ONE QUERY (#1157/#1160): the latest capture-health projection for ONE device — one `device_health` row, no scan, no on-device access needed.
list_device_events — The MULTI-PRODUCER device TELEMETRY event stream (#1160/#1208) — every DECISION and STATE TRANSITION reported about the capture pipeline by the iOS app OR by the PAC/proxy server (public.
list_device_audit_modes — Every device with AUDIT-mode telemetry currently armed — device_uuid + name, enabled, expires_at + expires_in, level, categories, who armed it (set_by_label) and when (set_at).
test_pac_connection — PROVE whether PAC capture actually works for ONE device — the "is it really working?