Conversation
|
@newswim is attempting to deploy a commit to the Sentry Team on Vercel. A member of the Team first needs to authorize it. |
|
I'm unable to review the deployment logs right now (due to insufficient permissions). Could the review bot share those with me? I'm surprised anything would be failing for this change. |
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
|
|
||
| <Expandable title="Setup Instructions" group="clients"> | ||
|
|
||
| Rovo Dev uses the stdio transport with a Sentry access token. Create a token in **User Settings → Auth Tokens** with these scopes: `org:read`, `project:read`, `project:write`, `team:read`, `event:write`. You may add more scopes if you wish. |
There was a problem hiding this comment.
Bug: The Rovo Dev setup instructions in docs/ai/mcp.mdx omit the required team:write access token scope, which will cause permission errors for users.
Severity: MEDIUM
Suggested Fix
Add team:write to the list of required access token scopes in the Rovo Dev setup instructions within docs/ai/mcp.mdx to match the requirements for the self-hosted setup and prevent user permission errors.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.
Location: docs/ai/mcp.mdx#L373
Potential issue: The documentation for setting up Rovo Dev omits the `team:write` scope
from the list of required access token scopes. Since Rovo Dev uses the same
stdio+access-token transport as the self-hosted setup, it requires the same permissions.
Users who create tokens following these instructions will encounter permission errors
when the MCP server attempts team write operations, such as creating or modifying teams.
This is inconsistent with the self-hosted setup instructions in the same file, which
correctly include `team:write`.
Did we get this right? 👍 / 👎 to inform future reviews.
|
This pull request has been automatically marked as stale because it has not had recent activity. If this PR is still relevant, please:
Thank you for your contribution! |
|
This pull request has been automatically closed due to inactivity. If you'd like to continue working on this, feel free to reopen the PR or create a new one. |
1 participant
Summary
Adds Rovo Dev to the MCP client instructions in docs/ai/mcp.mdx.
Rovo Dev is Atlassian's AI developer agent. Unlike most clients in this list, it uses the stdio transport with an access token rather than OAuth + Streamable HTTP, so it warrants its own setup section.
References
Screenshots
Collapsed view
Expanded view
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.