DebugBundle

MCP其他

提供方 debugbundle

其他 未标注 Token 社区 / 第三方 CursorCodexZed
查看接入方式

DebugBundle turns runtime failures, critical-path issues, and availability checks into incidents with full context, alerts, remote probes, and deterministic debug bundles for humans and AI agents.

一句话选型结论

按资料字段整理

DebugBundle 属于其他类 MCP 服务器,传输方式未标注,Token,可直接接入 Cursor、Codex、Zed,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类其他 传输方式未标注 鉴权Token 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

其他
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

mcp debugging observability incident response developer tools ai agents production

支持客户端

适用场景

mcpdebuggingobservability

安装与配置

未标注 Token
上游未给出传输方式
"command": "npx",\r

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
接入外部数据

把外部系统的数据接进对话。

自动化重复操作

把固定步骤交给模型跑。

补充工具能力

给模型补上它原本没有的能力。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Cursor、Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在其他场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、Codex 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
DebugBundle当前 未标注 未标注 未标注 有 未标注
gemini-cli 未标注 stdio · 本地进程 本地部署 有 2026-04-13
ext-apps 未标注 stdio · 本地进程 本地部署 有 2026-04-19
northcinder 未标注 stdio · 本地进程 本地部署 有 2026-08-23
fastctx 未标注 stdio · 本地进程 本地部署 有 2026-08-23
quickstart-resources 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

其他
字段来自项目仓库与公开索引,中文说明由本站标注
提供方debugbundle上游标注的维护方 debugbundle
分类其他本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

23.6 KB
来自项目仓库与上游目录的原文,未做删改

DebugBundle

Production debugging bundles for AI agents, with runtime error reporting and incident response.

DebugBundle provides runtime error reporting, crash reporting, incident response, endpoint health checks, and product analytics for humans and AI agents. It captures runtime failures, groups them into incidents, and publishes deterministic debug bundles. Its monitoring scope is customer-facing runtime behavior and endpoint health, not generic infrastructure metrics.

Works with AI coding agents including Codex, Claude Code, and Gemini CLI, as well as Cursor and GitHub Copilot. See the dedicated Codex, Claude Code, and Gemini CLI setup guides for native packages and direct MCP connections.

Why DebugBundle?

Modern AI agents are useful only when they get enough trustworthy context. DebugBundle packages the facts around a production incident into a versioned bundle instead of leaving agents to scrape dashboards, logs, traces, and chat threads.

Key properties:

  • Agent-native bundles: deterministic failure and improvement bundles with errors, requests, responses, logs, frontend context, deploy metadata, runtime details, and reproduction hints.
  • Interface parity: API, CLI, and MCP expose the same incident, bundle, probe, webhook, alert, project, and automation workflows.
  • Local-first setup: start without a cloud account by writing events to .debugbundle/local/events/, then connect to DebugBundle Cloud when ready.
  • Safe SDKs: SDK failures are swallowed internally, sensitive fields are redacted before transport, and duplicate storms are suppressed locally.
  • Self-hostable core: Compose-based stack for the web app, API, worker, Postgres, Redis, and S3-compatible object storage.

Public status pages

Project owners can publish a status page from Project → Health → Public status page. The button sits immediately left of Create health check and opens the shared settings modal. Choose a title and checks using searchable multi-select dropdowns; optionally add projects you own in the same account through Other projects. Turn on Enable public page to save and publish the initial settings immediately, then copy the stable link from its read-only input using the copy icon on the right. Paste it into your website. For an existing page, the switch saves visibility immediately; other title/project/check edits need Save status settings. New checks remain private; turning off the switch removes public access when the automatic save succeeds. Preview status page opens the saved public view in a dialog. Closing settings discards unsaved edits; reopening loads the saved configuration.

Public pages follow the device light/dark setting, including changes while open, independently of your dashboard theme preference. They reuse Health Status rows and 30-day availability history with a small clickable logo above the underlined Powered by DebugBundle attribution. Daily tooltips update on every adjacent block across the shared health views. Project/check names are public; endpoint URLs, errors, service/environment labels, incidents and account data remain private. API/CLI/MCP provide the same management operations. See the status-page contract and self-host deployment.

For local end-to-end verification, use the normal Docker stack (make dev), which initializes empty databases and migrates installed ones without resetting data. make dev-mock also simulates status settings, selection, preview, publish/unpublish and local anonymous pages for UI review. Restore real API routing with make dev-mock-off to verify persistence, authorization and migrations against the real stack. Follow the local verification checklist.

AnalyticsBundle

AnalyticsBundle extends debugging from incident evidence to product-usage evidence without turning DebugBundle into a long-term raw-event store. It is opt-in browser analytics for the questions a human or agent needs to improve a product: visits and active users, routes and funnels, device/browser/OS/language segments, feature use, friction markers, incident impact, and bounded structured journey replay.

  • Ask directly: API, CLI, and MCP expose aggregate metrics, journey patterns, opportunities, and generated AnalyticsBundles through the same project-authorized surface.
  • Generate by analysis unit: bundles describe a usage, funnel, route, friction, conversion, deploy, or incident-impact question. DebugBundle does not create one AnalyticsBundle per visit.
  • Keep evidence explainable: a generated bundle includes aggregate metrics, linked incidents/deploys, privacy-safe journey timelines, and deterministic journey-selection rank/basis for agent review.
  • Stay privacy- and cost-conscious: raw analytics inputs and retained journey samples expire; long-lived usage is aggregate rollups. Debug capture remains independent when analytics is disabled, unavailable, sampled out, quota-limited, or unhealthy.

See the repository public interface contract for API/CLI/MCP parity and the self-host guide for retention and upgrade behavior.

Quick Start

Choose the path that matches how you want to evaluate DebugBundle.

Cloud

Use Cloud when you are preparing a hosted deployment or want team-visible incidents, alerts, webhooks, GitHub automation, API access, and MCP access.```bash
npm install -g @debugbundle/cli
debugbundle setup
debugbundle login
debugbundle connect


`debugbundle connect` creates or selects a cloud project, creates a write-only project token, and updates `.debugbundle/local/connection.json`. Put the shown project token in your hosted environment:```bash
DEBUGBUNDLE_PROJECT_TOKEN=dbundle_proj_xxxxxxxxxxxx

Add the smallest SDK or ingestion path that matches your app, deploy it with the token configured, then verify ingestion:```bash
debugbundle verify cloud --project-id proj_01HXYZ... --trigger-5xx
debugbundle incidents --source cloud
debugbundle inspect inc_01HXYZ...


See the full Cloud quickstart and connect-to-cloud guide.

### Local-only

Use local-only mode when you want captured data and bundles to stay on the machine or storage volume where the SDK and CLI run.```bash
npm install -g @debugbundle/cli
debugbundle setup --project-mode local-only

Initialize an SDK in local mode where supported, or use debugbundle watch for existing logs. After triggering a test error:```bash
debugbundle process
debugbundle incidents --source local
debugbundle inspect inc_local_...


Local events are written under `.debugbundle/local/events/`; generated bundles are written under `.debugbundle/bundles/`. See the local-only guide.

## Install an SDK

All SDKs follow the same universal interface: `init`, `captureException`, `captureError`, `captureLog`, `captureRequest`, `captureMessage`, `setContext`, `probe`, and `flush`.

| Runtime      | Package                                           | Install                                        | Main docs                                                               |
| ------------ | ------------------------------------------------- | ---------------------------------------------- | ----------------------------------------------------------------------- |
| Node.js      | `@debugbundle/sdk-node`                           | `npm install @debugbundle/sdk-node`            | Node.js SDK                   |
| Browser      | `@debugbundle/sdk-browser`                        | `npm install @debugbundle/sdk-browser`         | Browser SDK                |
| Python       | `debugbundle-python`                              | `pip install debugbundle-python`               | Python SDK                  |
| PHP          | `debugbundle/sdk-php`                             | `composer require debugbundle/sdk-php`         | PHP SDK                        |
| Java         | `com.debugbundle:debugbundle-spring-boot-starter` | Maven or Gradle dependency                     | Java SDK                      |
| .NET         | `DebugBundle.AspNetCore` / `DebugBundle.Sdk`      | `dotnet add package DebugBundle.AspNetCore`    | .NET SDK                    |
| Go           | `github.com/debugbundle/debugbundle-go`           | `go get github.com/debugbundle/debugbundle-go` | Go SDK                          |
| Ruby         | `debugbundle`                                     | `gem install debugbundle`                      | Ruby SDK                      |
| Android      | `com.debugbundle:debugbundle-android`             | Maven or Gradle dependency                     | Android SDK                |
| iOS          | `DebugBundle`                                     | Swift Package Manager or CocoaPods             | iOS SDK                      |
| React Native | `@debugbundle/sdk-react-native`                   | `npm install @debugbundle/sdk-react-native`    | React Native SDK      |
| WordPress    | `debugbundle-wordpress`                           | WordPress.org plugin directory                 | WordPress plugin |

### Node.js```bash
npm install @debugbundle/sdk-node
``````typescript
import { debugbundle } from "@debugbundle/sdk-node";

debugbundle.init({
  projectToken: process.env.DEBUGBUNDLE_PROJECT_TOKEN,
  environment: "production",
  service: "api"
});

debugbundle.captureExceptions();
debugbundle.captureRejections();

Express, Fastify, Next.js, pino, winston, bunyan, local file transport, remote capture policy, probes, and browser relay handlers are supported.

Browser```bash

npm install @debugbundle/sdk-browser
``````typescript
import { createDebugBundleBrowserSdk } from "@debugbundle/sdk-browser";

const debugbundle = createDebugBundleBrowserSdk();

debugbundle.init({
transportMode: "relay",
endpoint: "/debugbundle/browser",
environment: "production",
service: "web"
});


For full-stack apps, prefer a backend browser relay so project tokens stay server-side. Same-origin relay paths are simplest; split frontend/backend deployments can use explicit browser relay mode with an absolute backend relay URL and backend origin allowlisting. Frontend-only deployments can send directly to DebugBundle Cloud with a dedicated public write-only token and an allowed-origin restriction. See Browser Relay Setup.

### Python```bash
pip install debugbundle-python
``````python
import os
import debugbundle

debugbundle.init(
    project_token=os.environ["DEBUGBUNDLE_PROJECT_TOKEN"],
    environment="production",
    service="api",
)

debugbundle.capture_exceptions()
debugbundle.capture_logging()

Django, Flask, FastAPI, Python logging, structlog, loguru, local file transport, remote capture policy, probes, and browser relay helpers are supported.

PHP```bash

composer require debugbundle/sdk-php
``````php
<?php

use DebugBundle\DebugBundle;

DebugBundle::init([
'projectToken' => getenv('DEBUGBUNDLE_PROJECT_TOKEN'),
'environment' => 'production',
'service' => 'api',
]);

DebugBundle::captureErrors();
DebugBundle::captureExceptions();
DebugBundle::captureShutdown();


Laravel, Symfony, Monolog, local file transport, remote capture policy, probes, and browser relay adapters are supported.

### Ruby```bash
gem install debugbundle
``````ruby
require &quot;debugbundle&quot;

DebugBundle.init(
  project_token: ENV[&quot;DEBUGBUNDLE_PROJECT_TOKEN&quot;],
  environment: &quot;production&quot;,
  service: &quot;api&quot;
)

DebugBundle.capture_exceptions

Rails, Rack, Sidekiq, Ruby Logger, Semantic Logger, local file transport, remote capture policy, probes, and browser relay handlers are supported.

Java```xml

<dependency>
<groupId>com.debugbundle</groupId>
<artifactId>debugbundle-spring-boot-starter</artifactId>
<version>0.1.0</version>
</dependency>
``````yaml
debugbundle:
project-token: ${DEBUGBUNDLE_PROJECT_TOKEN}
environment: production
service: api
project-mode: connected


The Spring Boot starter supports servlet request capture, MVC exception capture, Logback capture, remote config, probes, and an optional browser relay route.

### Go```bash
go get github.com/debugbundle/debugbundle-go
``````go
client := debugbundle.New(debugbundle.Config{
  ProjectToken: os.Getenv(&quot;DEBUGBUNDLE_PROJECT_TOKEN&quot;),
  Environment:  &quot;production&quot;,
  Service:      &quot;api&quot;,
})
defer func() { _ = client.Flush(context.Background()) }()

net/http, Gin, Echo, slog, zap, zerolog, local file transport, remote capture policy, probes, and browser relay handlers are supported.

WordPress

Install DebugBundle from the WordPress.org plugin directory, then open Settings -> DebugBundle and save your project token. The plugin bundles backend PHP capture, frontend browser capture, and a WordPress REST relay so the project token stays server-side.

CLI, API, and MCP

The CLI is the daily operational entry point:```bash
npm install -g @debugbundle/cli
debugbundle setup
debugbundle doctor
debugbundle verify local
debugbundle verify cloud --trigger-5xx
debugbundle incidents
debugbundle inspect <incident-id>


Automation can use the HTTP API directly or the MCP server for agent workflows:

- API reference:
- CLI reference:
- MCP docs:
- MCP distribution channels:
- OpenAI Plugin candidate:
- Bundle schema:

Marketplace-managed MCP clients can run `npx @debugbundle/mcp` and provide `DEBUGBUNDLE_MEMBER_TOKEN` in the MCP server environment. The official MCP Registry name is `com.debugbundle/mcp`; project tokens are SDK write-only ingestion credentials and must not be used for MCP retrieval or management.

The separate OpenAI Plugin `1.0.0` production candidate combines a tailored skill with an OAuth-protected twenty-three-tool read-only remote projection plus the owner-approved existing-app consent, synthetic-reviewer, and Settings revocation surfaces. Its nine analytics tools expose bounded aggregate usage, route, device, acquisition, action, funnel, journey-pattern, and incident-impact metrics while excluding individual journeys, custom dimensions, analytics bundles/opportunities, and mutations. It is active at the permanent `https://mcp.debugbundle.com/mcp` origin for owner-approved Developer Mode validation, preserves the stdio/OpenClaw surface, and is not submitted, published, or publicly installable.

For local visual review without a real provider interaction, run `make dev-openai-plugin-preview` and open . The opt-in development route uses the production UI components with deterministic synthetic data and provides every consent/reviewer/Settings state, all 64 scope subsets, and 390 px, 768 px, and 1280 px iframe viewports. Its actions stay in browser memory and never call OAuth, reviewer, grant, or revocation APIs. The route is absent from production builds, and preview evidence does not replace manual accessibility, MCP Inspector, outside-network reviewer, ChatGPT Developer Mode, deployed, submission, or publication validation.

## Repository Layout```text
apps/
  api/       Fastify ingestion and retrieval API
  worker/    BullMQ processing worker for normalization, grouping, bundles, alerts, and webhooks
  cli/       @debugbundle/cli command-line interface
  mcp/       @debugbundle/mcp server for agent workflows
  web/       React/Vite app for interactive project and incident management
packages/
  auth/              Auth, sessions, token generation, token hashing
  bundle-engine/     Deterministic bundle assembly
  event-normalizer/  Event validation, normalization, classification, fingerprinting
  log-parser/        CLI log ingestion parser registry
  redaction/         Sensitive data scrubbing
  retrieval-client/  Shared retrieval API client used by CLI and MCP
  shared-types/      Zod schemas, TypeScript types, bundle/event contracts
  storage/           Postgres, Redis, S3-compatible storage adapters and migrations
sdks/
  debugbundle-js/         Local clone of the JS SDK repo
  debugbundle-python/     Local clone of the Python SDK repo
  debugbundle-php/        Local clone of the PHP SDK repo
  debugbundle-java/       Local clone of the Java SDK repo
  debugbundle-go/         Local clone of the Go SDK repo
  debugbundle-wordpress/  Local clone of the WordPress plugin repo
  debugbundle-ruby/       Local clone of the Ruby SDK repo
site/
  Public docs, marketing, reference, and blog site clone

The SDKs are standalone repositories under the debugbundle GitHub organization. This core repository owns the product services, shared contracts, CLI/MCP surfaces, and core-owned shared JS packages.

Local Development

Use the Make targets so routine commands run in Docker-scoped environments.```bash
make install
make infra-up
make infra-bootstrap
make dev


Local services:

| Service       | Default                 |
| ------------- | ----------------------- |
| Web app       | `http://localhost:5291` |
| API           | `http://localhost:3003` |
| Postgres      | `localhost:5434`        |
| Redis         | `localhost:6380`        |
| LocalStack S3 | `localhost:4567`        |

Useful checks:```bash
make lint
make typecheck
make test
make build
make ci

make dev requires DEBUGBUNDLE_PROBE_TRIGGER_SECRET and ANALYTICS_HASH_SECRET in .env. Start from .env.example, then keep local-only overrides in .env.local when needed.

Populated UI preview

After make install, run make dev-mock and open .
It restarts only the web container and automatically signs the preview in as
demo@example.test. Synthetic projects, incidents, improvements, 30-day health
history, alert/capture rules, webhook endpoints and delivery history, project and
member tokens, members/invitations, billing, provider connections, and GitHub
deliveries are served locally, so the data works in your ordinary browser.
SayCheese has analytics enabled with sample funnels, flows, journeys, opportunities
and generated artifacts. TaskTime includes empty and analytics-disabled states.

Project edits, incident/improvement actions, rule and health-check edits, webhook
creation/tests, token creation/revocation, invitations/member edits, probe
activation, weekly reports, repository selection, and analytics settings/flows/
funnels/bundle generation and public status publication are simulated in memory.
Public status pages start private; select checks and publish in Project Health to
open a loopback share link. Mock project/check IDs use UUIDs so the normal strict
forms work, including newly created records. Publication choices paginate, new
checks remain private, and restarting resets publications along with other edits.
Failed-delivery clearing uses
the normal browser-only behavior. Billing checkout and portal links stay in the
local preview; capacity changes only update mock state. Mock credentials are
deliberately unusable with real installations. No real checks, notifications,
GitHub dispatches, OAuth interactions, payments or database writes are made.
Unknown API operations still return an explicit preview error without contacting
the backend. External provider authorization and private operator tools require
normal development. After a mock logout, use any valid email and code 123456 to
return to the demo account; the same code is used for simulated account deletion.

  • Run make dev-mock again to reset the simulated server data. Browser preferences
    and cleared-delivery IDs remain in local storage; use Show cleared to inspect them.
  • Run make dev-mock-off to return the frontend to your real local API.
  • The preview binds to loopback, blocks foreign origins and intercepts unknown API
    paths rather than forwarding them. It requires development serve mode, is absent
    from production builds and disables frontend telemetry even if local env enables it.

Self-Hosting

The supported self-host bootstrap lives in deploy/selfhost/.bash git clone https://github.com/debugbundle/debugbundle.git cd debugbundle/deploy/selfhost cp .env.example .env docker compose up -d

The self-host stack includes the web app, API, worker, PostgreSQL, Redis, and LocalStack S3. See Self-Hosting and deploy/selfhost/README.md.

Documentation

  • Public docs:
  • Quickstart:
  • Installation:
  • SDKs:
  • Agent workflows:
  • System overview: SYSTEM_OVERVIEW.md
  • Architecture map: ARCHITECTURE_MAP.md
  • Requirements: spec/requirements.md
  • Acceptance criteria: spec/acceptance.md
  • Public interfaces: contracts/public-interfaces.md

Release Model

The canonical public product release is the root debugbundle repository tag and GitHub Release (v*). Package-specific releases are separate:

  • cli-v* for @debugbundle/cli
  • mcp-v* for @debugbundle/mcp
  • shared-js-v* for @debugbundle/shared-types and @debugbundle/redaction

Standalone SDK repositories publish and version their own release surfaces independently:

  • debugbundle-js for @debugbundle/sdk-node and @debugbundle/sdk-browser
  • debugbundle-python for debugbundle-python
  • debugbundle-php for debugbundle/sdk-php
  • debugbundle-java for Maven artifacts
  • debugbundle-go for Go modules
  • debugbundle-wordpress for the WordPress plugin

The v1 release train publishes dependency roots before dependent wrappers:

  1. Publish @debugbundle/shared-types and @debugbundle/redaction from the core repo first.
  2. Publish @debugbundle/sdk-node and @debugbundle/sdk-browser from debugbundle-js after the matching shared-package version exists on npm.
  3. Publish independent SDK and package families whose artifacts do not bundle another DebugBundle SDK.
  4. Publish React Native after the Android and iOS native SDK versions it delegates to are live and smoke-tested.
  5. Publish WordPress after the PHP SDK and browser SDK versions it requires are live and smoke-tested, then rebuild the bundled browser asset.
  6. Bump hosted dogfooding manifests only after the referenced registry versions exist.
  7. Create the canonical core GitHub Release after package-specific release workflows pass.

Our own hosted/source-deployed dogfooding surfaces intentionally consume published packages rather than implicit workspace links. After a successful registry publish, bump the pinned versions in the root package.json, hosted app apps/web/package.json, and public-site site/package.json before running hosted validation or deployment.

Contributing

Read CONTRIBUTING.md before opening a pull request. The short version:

  • Keep app/package boundaries strict.
  • Add or update tests for behavior changes.
  • Run make lint, make typecheck, make test, and make build before asking for review.
  • Update docs, contracts, and public interface references when behavior changes.

Security

Do not report vulnerabilities in public issues. Use GitHub private vulnerability reporting for this repository:

See SECURITY.md for scope and response expectations.

License

DebugBundle core, SDKs, and executable developer tools use Apache-2.0. Service-required exceptions are limited to the WordPress plugin (GPL-2.0-or-later) and portable ClawHub/Smithery instruction skill (MIT-0). See the licensing policy.

Shared shadcn styles

The web app vendors the unchanged shadcn 4.1.2 Tailwind stylesheet in
apps/web/src/styles/shadcn.css, including its upstream MIT license. This preserves
the current component animations and data variants without installing the component
generator and its unused vulnerable glob-parser dependency in the app. Existing
shadcn components and components.json remain the source of the UI. Inspect component docs with make ui-component-docs UI_COMPONENTS=&#x27;dialog input-group&#x27; and preview registry changes with make ui-component-add UI_COMPONENTS=input-group UI_COMPONENT_FLAGS=&#x27;--dry-run&#x27;. Review existing component differences before applying changes; preserve local primitives and shared utilities. Run the
component generator separately through its package runner when needed, and review
any generated dependency/import changes against the dependency audit before adoption.

make audit checks the installed dependency graph for high and critical advisories;
core CI and core publication enforce the same threshold. Dependency refreshes use
bounded vulnerable-version overrides and preserve independently published SDK pins.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
DebugBundle 怎么安装?

在客户端按下面的安装命令接入:"command": "npx",\r。装完在客户端配置里引用同一个包或端点。

DebugBundle 怎么在 Cursor、Codex、Zed 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

DebugBundle 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

DebugBundle 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

DebugBundle 支持哪些客户端?

资料标注支持 Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

DebugBundle 能提供哪些能力?

资料显示能力标签包括 mcp、debugging、observability、incident response、developer tools、ai agents。具体工具清单以官方文档为准。

DebugBundle 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。