@debugbundle/mcp 1.6.1 → 1.6.3

package/README.md

@@ -1,6 +1,6 @@
 # @debugbundle/mcp
 
-MCP server for production debugging bundles and incident workflows for AI agents. DebugBundle lets agents inspect incidents, deterministic bundles, reproductions, probes, hosted health checks, alerts, webhooks, projects, and setup state through the same management surface as the API and CLI.
+MCP server for runtime error reporting, crash reporting, incident response, endpoint health checks, debug bundles, and product analytics. DebugBundle lets agents inspect customer-facing incidents, deterministic bundles, product-usage evidence, reproductions, probes, alerts, webhooks, projects, and setup state through the same management surface as the API and CLI. It is production debugging infrastructure, not a generic infrastructure-monitoring or observability platform.
 
 ## Install
 
@@ -40,6 +40,7 @@ Use `npx -y @debugbundle/mcp` in clients that require noninteractive package exe
 | --- | --- | --- |
 | Generic local MCP client | `npx @debugbundle/mcp` | stdio transport |
 | Claude Desktop local MCP | local MCP server config | uses local machine auth/config |
+| Claude Code plugin | `/plugin marketplace add debugbundle/debugbundle` | installs bundled MCP config and DebugBundle skill |
 | Cursor | MCP config with `npx @debugbundle/mcp` | stdio transport |
 | VS Code / GitHub MCP Registry | `com.debugbundle/mcp` | official registry metadata |
 | OpenClaw / ClawHub | DebugBundle skill plus MCP config | use the published skill for workflow guidance |
@@ -48,6 +49,34 @@ Use `npx -y @debugbundle/mcp` in clients that require noninteractive package exe
 
 DebugBundle does not expose a hosted remote MCP endpoint today; this package is the local stdio path.
 
+## Claude Desktop
+
+In Claude Desktop, open Settings > Developer, edit the local MCP config, and add:
+
+```json
+{
+  "mcpServers": {
+    "debugbundle": {
+      "command": "npx",
+      "args": ["-y", "@debugbundle/mcp"]
+    }
+  }
+}
+```
+
+Run `debugbundle login` first to reuse local CLI auth state, or add `DEBUGBUNDLE_MEMBER_TOKEN` to the server environment for managed/headless use. Set `DEBUGBUNDLE_API_URL` only for self-hosted or non-default API hosts.
+
+## Claude Code Plugin
+
+Claude Code users can add DebugBundle's first-party marketplace from this repository:
+
+```text
+/plugin marketplace add debugbundle/debugbundle
+/plugin install debugbundle@debugbundle
+```
+
+The plugin package lives at `apps/mcp/claude-code/debugbundle`, bundles a Claude Code skill, and starts the MCP server with the current published `@debugbundle/mcp` version. It is also structured for Claude community marketplace review; do not describe it as listed in `claude-community` until Anthropic accepts and publishes it.
+
 ## Authentication
 
 | Mode | Use | Notes |
@@ -61,10 +90,26 @@ DebugBundle does not expose a hosted remote MCP endpoint today; this package is
 
 - List active incidents and fetch full incident context.
 - Fetch deterministic debug bundles and reproduction artifacts.
+- Query aggregate usage, routes, device/browser/OS/language segments, referrers, actions, funnels, and journey patterns without waiting for an analysis artifact through `get_usage_summary`, `get_route_metrics`, `get_device_breakdown`, `get_action_metrics`, `get_funnel_analysis`, and related reads.
+- Inspect retained redacted journey samples, analytics opportunities, and generated AnalyticsBundles; request a bounded analysis artifact when aggregate metrics alone are insufficient.
+- Read analytics settings before proposing privacy, retention, consent, capture, or approved custom-dimension changes; update them only with explicit owner/admin intent.
+- List saved analytics funnels and, with owner/admin access, create, update, or archive reusable funnel definitions through `list_saved_analytics_funnels`, `create_saved_analytics_funnel`, `update_saved_analytics_funnel`, and `archive_saved_analytics_funnel`.
 - Inspect hosted health checks, probes, alerts, webhooks, projects, members, billing, capture policy, and GitHub automation state.
 - Run local and hosted verification through tools such as `verify_local`, `verify_cloud`, `doctor`, `smoke`, and `analyze`.
 - Resolve or reopen incidents after verification.
 
+For analytics questions, use direct aggregate tools first and generate an AnalyticsBundle only when a bounded analysis needs a durable artifact. The product does not create one bundle per visit.
+
+## Troubleshooting
+
+| Symptom | Check |
+| --- | --- |
+| Node.js launch failure | Use Node.js 22.x through 26.x. Configure the client to use a supported `node` or `npx` runtime. |
+| Missing local auth | Run `debugbundle login`, or set `DEBUGBUNDLE_MEMBER_TOKEN` for headless and managed clients. |
+| Invalid token | Use a `dbundle_mem_` member token. Project tokens are SDK ingestion-only credentials. |
+| Wrong API host | Leave `DEBUGBUNDLE_API_URL` unset for DebugBundle Cloud; set it only for self-hosted or non-default API hosts. |
+| Local repo not initialized | Run `debugbundle setup` before local-only diagnostics, local bundle analysis, or generated project-skill workflows. |
+
 ## Links
 
 - Docs: https://debugbundle.com/docs/mcp