Repository navigation
x: request broadcast.read and broadcast.write scopes (2.9.0) - #727
Closed
santiagomed wants to merge 3 commits into
Closed
santiagomed wants to merge 3 commits into
santiagomed wants to merge 3 commits into
Conversation
The livestream tools on https://api.x.com/mcp (broadcasts, scheduled broadcasts, broadcast chat moderators and mutes, and stream sources) return 403 for missing scopes, because the plugin never asks for broadcast.read or broadcast.write. Request both after calls.write and list them in the README.
Missing broadcast or source tools, or a 403 for broadcast.read / broadcast.write, while other X tools work means the connection predates the new scopes. Say to reconnect, the same as for X Chat and call scopes, instead of error 2.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The 18 livestream tools on
https://api.x.com/mcp(broadcasts, scheduled broadcasts, broadcast chat moderators and mutes, and stream sources) return 403 for missing scopes, because the X plugin never requestsbroadcast.readorbroadcast.write.What
mcp.json: requestsbroadcast.readandbroadcast.write, aftercalls.write. The README's MCP snippet and "Scopes requested" list match.skills/x-api-mcp-guide/SKILL.md: scope and reconnect guidance only. Missing livestream tools, or a 403 forbroadcast.read/broadcast.write, while other X tools work is not error 2. A new Livestream scopes section tells the user to reconnect, the same as for X Chat and call scopes.plugin.jsonand the CHANGELOG. 2.8.0 is already claimed by x: X Chat image send via MCP, pin chatxdk<0.6, reinstall note (2.8.0) #719, which is still open.Before merging
https://api.x.com/mcp. Merge this only after it lands.Testing
node scripts/validate-plugins.mjs: all plugins validated.mcp.jsonand both README lists match each other and match the scope set D1386218 advertises forhttps://api.x.com/mcp.Note
Low Risk
Plugin metadata and agent guidance only; scope expansion requires user reconnect and depends on server-side auth metadata (D1386218) for end-to-end behavior.
Reviewed by Cursor Bugbot for commit b47f9d8. Bugbot is set up for automated code reviews on this repo. Configure here.