You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(mcp-core): Expose get_sentry_resource by default (#852)
Promote get_sentry_resource to the stable tool surface and hide the
legacy issue and trace detail tools behind it.
This fixes the confusion from GH-850 where get_sentry_resource and
breadcrumbs were only reachable in experimental mode. The legacy detail
handlers still exist so get_sentry_resource can compose them internally,
but they are now marked internal-only and filtered out of server
registration, generated definitions, plugin allowedTools, and
use_sentry's embedded tool surface.
I also updated public guidance and plugin prompts to point to
get_sentry_resource instead of the legacy tool names, and regenerated
the derived definitions so the stable and experimental plugin manifests
stay in sync.
FixesGH-850
---------
Co-authored-by: Codex <codex@openai.com>
Copy file name to clipboardExpand all lines: packages/mcp-cloudflare/src/server/app.ts
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ When scoped, tools automatically default to the constrained org/project and unne
39
39
40
40
### Query Parameters
41
41
42
-
- \`?experimental=1\` — Enable experimental, forward-looking features and tools
42
+
- \`?experimental=1\` — Enable forward-looking tool variants and experimental features
43
43
- \`?agent=1\` — Agent mode: exposes a single \`use_sentry\` tool that handles natural language requests via an embedded AI agent (roughly doubles response time)
44
44
45
45
Parameters can be combined: \`${baseUrl}/mcp/my-org/my-project?experimental=1\`
0 commit comments