@debugbundle/mcp 1.13.0 → 1.14.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -42,7 +42,7 @@ Use `npx -y @debugbundle/mcp` in clients that require noninteractive package exe
42
42
  | Claude Desktop local MCP | local MCP server config | uses local machine auth/config |
43
43
  | Claude Code plugin | `/plugin marketplace add debugbundle/debugbundle` | installs bundled MCP config and DebugBundle skill |
44
44
  | Codex developer plugin | `codex plugin add debugbundle-codex@debugbundle` | repository marketplace; local MCP and workflow skill |
45
- | Codex direct MCP | `codex mcp add debugbundle -- npx -y @debugbundle/mcp@1.13.0 --local-auth` | app, CLI, and IDE on the same host |
45
+ | Codex direct MCP | `codex mcp add debugbundle -- npx -y @debugbundle/mcp@1.14.0 --local-auth` | app, CLI, and IDE on the same host |
46
46
  | Cursor | MCP config with `npx @debugbundle/mcp` | stdio transport |
47
47
  | VS Code / GitHub MCP Registry | `com.debugbundle/mcp` | official registry metadata |
48
48
  | OpenClaw / ClawHub | DebugBundle skill plus MCP config | use the published skill for workflow guidance |
@@ -112,6 +112,14 @@ The plugin package lives at `apps/mcp/claude-code/debugbundle` and bundles a Cla
112
112
  - 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`.
113
113
  - Inspect hosted health checks, probes, alerts, webhooks, projects, members, billing, capture policy, and GitHub automation state.
114
114
  - Run local and hosted verification through tools such as `verify_local`, `verify_cloud`, `doctor`, `smoke`, and `analyze`.
115
+
116
+ `verify_app_event` provides real SDK-driven app proof, matching the CLI's
117
+ `verify cloud --expect-app-event`. Pass `projectId` and at least one of `service`,
118
+ `traceId`, or `requestId`; `environment`, `maxAgeMinutes`, and `authFilePath` are
119
+ optional. It reads existing incidents/bundles and never sends synthetic events.
120
+ The existing `verify_cloud` schema and description remain unchanged. The new tool
121
+ is available through ordinary and local-auth stdio MCP and its OpenClaw projection;
122
+ hosted read-only and restricted agent catalogs remain unchanged.
115
123
  - Resolve or reopen incidents after verification.
116
124
 
117
125
  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.
@@ -147,3 +155,14 @@ For analytics questions, use direct aggregate tools first and generate an Analyt
147
155
  ## License
148
156
 
149
157
  Apache-2.0.
158
+
159
+ `disconnect_github_installation` calls the existing organization-wide disconnect
160
+ route. It requires the active organization's owner and removes repository assignments
161
+ for all its projects, including cleanup after downgrade. It does not uninstall the
162
+ App on GitHub. Install/reconnect uses the dashboard browser flow to retain the signed
163
+ state cookie. This additive tool brings the ordinary/local-auth catalog to 130 tools;
164
+ the hosted 23-tool and restricted five-tool profiles remain unchanged.
165
+
166
+ `test_webhook_event` accepts all eight supported webhook events through the existing
167
+ scoped test service. The legacy `test_webhook` schema remains verification-only.
168
+ Both queue a signed synthetic envelope without creating real incidents or bundles.