Skip to content

Make Sentry MCP queries explicit in smoke OTEL workflow - #32185

Merged
mnkiefer merged 2 commits into
mainfrom
copilot/investigate-sentry-mcp-tools
May 14, 2026
Merged

mnkiefer merged 2 commits into
mainfrom
copilot/investigate-sentry-mcp-tools

Conversation

Copilot AI commented May 14, 2026

Copy link
Copy Markdown
Contributor

Bug Fix

The smoke OTEL workflow was relying on npx auto-containerization for the Sentry MCP server, which made Sentry span/event query tools unavailable through MCP in this path. This change makes the Sentry MCP launch explicit and updates the compiled lockfile to match.

What was the bug?

  • Sentry MCP in smoke-otel-backends
    • The workflow defined Sentry with command: "npx" / args: [...].
    • In this workflow path, that implicit setup did not reliably expose the Sentry MCP query tools needed for span/event access.

How did you fix it?

  • Explicit Sentry MCP container config

    • Replaced the implicit npx command form with an explicit containerized stdio MCP config:
      • container: "node:lts-alpine"
      • entrypoint: "npx"
      • entrypointArgs: ["@sentry/mcp-server@0.33.0"]
    • Kept the existing allowed Sentry tools unchanged.
  • Recompiled generated workflow

    • Regenerated .github/workflows/smoke-otel-backends.lock.yml so the compiled workflow uses the explicit Sentry MCP container configuration.

Example

mcp-servers:
  sentry:
    container: "node:lts-alpine"
    entrypoint: "npx"
    entrypointArgs: ["@sentry/mcp-server@0.33.0"]
    allowed:
      - whoami
      - find_organizations
      - find_projects
      - search_events
      - get_trace_details

Recompiled output

  • Lockfile alignment
    • Updated the compiled lockfile so the runtime uses the same explicit Sentry MCP definition as the source workflow.

Copilot AI and others added 2 commits May 14, 2026 17:50
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
@mnkiefer
mnkiefer marked this pull request as ready for review May 14, 2026 18:08
Copilot AI review requested due to automatic review settings May 14, 2026 18:08

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Smoke OTEL Backends workflow to launch the Sentry MCP server via an explicit containerized stdio configuration (instead of relying on npx implicit behavior), and regenerates the compiled lock workflow so runtime configuration matches the source.

Changes:

  • Switched Sentry MCP definition from command/args to explicit container/entrypoint/entrypointArgs in the source workflow.
  • Regenerated .github/workflows/smoke-otel-backends.lock.yml to reflect the new Sentry MCP container configuration.
Show a summary per file
File Description
.github/workflows/smoke-otel-backends.md Makes Sentry MCP launch explicit via a Node container + npx entrypoint for reliable access to Sentry query tools.
.github/workflows/smoke-otel-backends.lock.yml Recompiled workflow output to align runtime MCP gateway config (and pinned images) with the updated source workflow.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 2/2 changed files
  • Comments generated: 0

@mnkiefer
mnkiefer merged commit bf49169 into main May 14, 2026
4 checks passed
@mnkiefer
mnkiefer deleted the copilot/investigate-sentry-mcp-tools branch May 14, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants