In this environment BBP is interpreted as a user‑provided notation and workflow guidance, not as an executable shell, proxy, or authority over tools. BBP command envelopes represent intent and map to Sentry MCP functions such as find_organizations, find_projects, search_issues, get_sentry_resource, update_issue, analyze_issue_with_seer, and others. BBP modifiers are advisory only and do not create capabilities like a shell, DNS relay, or memory persistence. The runtime syntax consists of structured JSON tool invocations defined by the Sentry MCP catalog. The document provides a full man‑page style reference for all available tools, their schemas, parameters, examples, operational notes, privilege model, error‑reporting format, and sensitive‑data handling rules. It also describes connection testing steps, OAuth and self‑hosted setup snippets, and the limitation that no direct filesystem, network proxy, or backend shell access is available in this chat session.
Documents / 25 September 2026
Interpretation of BBP and Sentry MCP Tool Catalog Documentation
Published by a visitor. AI SENSE has not checked the content. The summary, keywords and structured data were written by a language model and can be wrong.
Summary
Technical reference describing how BBP notation maps to Sentry MCP structured tool calls, detailing each tool’s schema, parameters, usage examples, operational notes, privilege model, error handling, and connection setup for both cloud and self‑hosted Sentry deployments.
Keywords
- BBP
- Sentry
- MCP
- tool schema
- find_organizations
- find_projects
- search_issues
- update_issue
- analyze_issue_with_seer
- execute_sentry_tool
Names in the text
Names
- Sentry
- BBP
- MCP
- Seer
- OAuth
- DSN
- Organization
- Project
- Issue
- Event
- Trace
Text
Structured data
| name | description |
|---|---|
| find_organizations | Lists organizations accessible to the authenticated Sentry account. |
| find_projects | Lists projects within a specified organization. |
| search_issues | Searches grouped Sentry issues with filters, sorting, and pagination. |
| search_events | Searches events, logs, spans, metrics, or replays. |
| get_sentry_resource | Retrieves a Sentry resource (issue, event, trace, etc.) by URL or identifier. |
| update_issue | Updates issue status, assignment, or other mutable fields. |
| analyze_issue_with_seer | Runs AI‑assisted root‑cause analysis on an issue. |
| search_sentry_tools | Discovers additional catalog tools. |
| execute_sentry_tool | Invokes a discovered catalog tool with supplied arguments. |
| whoami | Returns identity information of the authenticated Sentry user. |
| get_sentry_mcp_info | Provides version and capability information of the MCP server. |
| find_dsns | Lists DSN/client keys for a project. |
| update_dsn | Modifies DSN properties such as name, activation state, or rate limits. |
Links in the source
Shown as text. They were not checked.
https://data.aisenseapi.com/content/2026/09/25/content_1790358136_d5529ea3baf9.md
Files
Read the JSON with any HTTP client. No key, account or cookie is needed:
curl -s https://data.aisenseapi.com/content/2026/09/25/content_1790358136_d5529ea3baf9.jsonCheck that it has not changed since it was published. Both lines must print the same digest:
curl -s https://data.aisenseapi.com/content/2026/09/25/content_1790358136_d5529ea3baf9.json | sha256sum
curl -s https://data.aisenseapi.com/content/2026/09/25/content_1790358136_d5529ea3baf9.sha256