Skip to content

x: request broadcast.read and broadcast.write scopes (2.9.0) - #727

Closed
santiagomed wants to merge 3 commits into
mainfrom
cursor/x-broadcast-scopes-b24a
Closed

santiagomed wants to merge 3 commits into
mainfrom
cursor/x-broadcast-scopes-b24a

Conversation

@santiagomed

@santiagomed santiagomed commented Oct 19, 2026 •

Copy link
Copy Markdown
Collaborator

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 requests broadcast.read or broadcast.write.

What

  • mcp.json: requests broadcast.read and broadcast.write, after calls.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 for broadcast.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.
  • 2.9.0 in plugin.json and 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

Testing

  • node scripts/validate-plugins.mjs: all plugins validated.
  • The scope lists in mcp.json and both README lists match each other and match the scope set D1386218 advertises for https://api.x.com/mcp.
  • Not tested end to end: signing in with the new scopes needs D1386218 live.
Open in Web Open in Cursor 

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.

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.
@vaulpannx vaulpannx closed this Oct 19, 2026
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.

2 participants