Skip to content

Enable BugSnag error and performance on by default #282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tomlongridge wants to merge 5 commits into
base: main
Choose a base branch
from
+2,330 −222
Open

Enable BugSnag error and performance on by default #282

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
42b80ea
feat(common): add tool OTEL instrumentation (#268)
sazap10 Nov 28, 2025
7cc5bdc
feat: bugsnag performance telemetry
tomlongridge Dec 11, 2025
7f31810
use node scripting instead of sed
tomlongridge Dec 15, 2025
c8b72b7
fix docker build
tomlongridge Dec 15, 2025
3bfb4ea
fix docker build (again)
tomlongridge Dec 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,16 +5,18 @@ WORKDIR /app

COPY src/ ./src/
COPY package.json package-lock.json tsconfig.json ./
COPY scripts/set-release-stage.js ./scripts/set-release-stage.js

RUN --mount=type=cache,target=/root/.npm npm ci

RUN npm run build
RUN npm run build:production

FROM node:22-alpine AS release

COPY --from=builder /app/dist /app/dist
COPY --from=builder /app/package.json /app/package.json
COPY --from=builder /app/package-lock.json /app/package-lock.json
COPY --from=builder /app/scripts/set-release-stage.js /app/scripts/set-release-stage.js
Comment thread
tomlongridge marked this conversation as resolved.

ENV NODE_ENV=production

Expand Down
11 changes: 5 additions & 6 deletions docs/products/SmartBear MCP Server/getting-started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ The SmartBear MCP Server supports multiple SmartBear Hubs, each requiring its ow

## Configure Environment Variables

The following environment variables based on which SmartBear hubs you want to access:
The following environment variables based on which SmartBear products you want to access:

```shell
# Required for BugSnag tools
Expand All @@ -91,9 +91,6 @@ export PACT_BROKER_TOKEN=your-pactflow-api-token
export PACT_BROKER_USERNAME=your-username
export PACT_BROKER_PASSWORD=your-password

# Optional: Enable error reporting for the MCP server itself
export MCP_SERVER_BUGSNAG_API_KEY=your-monitoring-api-key

# Required for QMetry tools
export QMETRY_API_KEY=your-qmetry_api_key

Expand All @@ -107,8 +104,6 @@ export ZEPHYR_BASE_URL="https://api.zephyrscale.smartbear.com/v2"

```

> ⚠️ The `MCP_SERVER_BUGSNAG_API_KEY` is used for monitoring the MCP server itself and should be different from your main application's API key.

## MCP Host Configuration

Configure your MCP host to connect to the SmartBear server. Below are examples for popular clients. In all cases, replace `<PATH_TO_SMARTBEAR_MCP>` with the absolute path to your cloned repository.
Expand Down Expand Up @@ -461,6 +456,10 @@ To run the built server locally in VS Code, add the following configuration to 

```

### BugSnag instrumentation

The MCP server includes built-in BugSnag instrumentation to monitor its own health and performance. To disable this, or send it to your own dashboard, set the `MCP_SERVER_BUGSNAG_API_KEY` environment variable to an empty string or a different BugSnag API key. This key should be different from the one used for your main application to avoid mixing error reports.

### Testing with MCP Inspector

To test the MCP server locally before integrating with your preferred host, you can use the MCP Inspector:
Expand Down
Loading