X plugin: livestream tools (sources, broadcasts, scheduled broadcasts, chat moderation)

[m-rosinsky]

Why

The X MCP server (https://api.x.com/mcp) now serves 18 livestream tools: stream sources, broadcasts, scheduled broadcasts, chat moderators and chat mutes. The X plugin doesn't request the broadcast.* scopes and its guide doesn't mention the tools, so agents can't use them, and couldn't do it safely if they could.

What

• mcp.json: requests broadcast.read and broadcast.write.
• skills/x-api-mcp-guide/SKILL.md: a new Livestreams section, plus matching entries in the description, the on-connect capabilities, scopes, cost, common tasks and "Don't":
  • Tool table with scopes for list_sources, get_source, create_source, update_source, delete_source, list_broadcasts, get_broadcast, list_scheduled_broadcasts, get_scheduled_broadcast, create_scheduled_broadcast, update_scheduled_broadcast, delete_scheduled_broadcast, go_live_scheduled_broadcast, get_chat_moderators, add_chat_moderator, remove_chat_moderator, mute_broadcast_chat_user and unmute_broadcast_chat_user.
  • "Schedule a livestream" recipe: take a source from list_sources, or create one with a region; resolve the start time in the owner's timezone; call create_scheduled_broadcast with source_id and scheduled_start_ms.
  • Going live right now is not supported. There's no tool to start, publish or end an immediate broadcast. A schedule starts on its own at its start time, or through go_live_scheduled_broadcast when it was created with manual_publish: true.
  • Safety:
    • writes only when the owner asked;
    • a source's id is its stream key, so it stays out of the chat;
    • create_source isn't idempotent, so list before retrying;
    • id and full-replace rules for update_scheduled_broadcast;
    • moderators apply to all broadcasts (at most 20), and mutes need a running broadcast;
    • the Premium-or-1,000-followers 403 is account eligibility, not credits.
  • Cost: livestream tools are free (these routes don't bill).
  • Missing tools while other X tools work means reconnect, the same as calls and Chat.
• 2.8.0: plugin.json version, description and livestream keyword, the CHANGELOG entry, and the marketplace and README listing text.

Existing installs need to sign in to X again to pick up the new scopes.

Testing

• node scripts/validate-plugins.mjs: all plugins validated.
• The flow the skill describes was run against prod https://api.x.com/mcp with an OAuth2 user token:
  • tools/list lists all 18 tools;
  • list_sources, create_source, get_source, update_source and delete_source round-trip;
  • create_scheduled_broadcast scheduled a broadcast for tomorrow at 3pm ET on a listed source;
  • get_scheduled_broadcast read it back, and delete_scheduled_broadcast removed it.

---

Note

Low Risk
Config and documentation only; OAuth scope expansion requires user reconnect but does not change core plugin runtime code or shared auth infrastructure.

Overview
X plugin 2.8.0 enables agents to use the MCP livestream APIs by requesting broadcast.read and broadcast.write in mcp.json, and documents the full workflow in the X MCP skill.

The new Livestreams guidance covers 18 tools (sources, broadcasts, scheduled broadcasts, chat moderators/mutes): scheduling recipe, free-tool billing rules, reconnect when scopes are missing (same pattern as calls/Chat), and guardrails—no instant go-live, owner consent for writes, stream keys treated as secrets, non-idempotent create_source, and Premium/1k-follower eligibility errors.

Marketing copy updates in README, marketplace.json, and plugin.json (version, keyword, description). CHANGELOG notes that existing installs must re-sign in for the new scopes.

^{Reviewed by Cursor Bugbot for commit 42b357b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.}

^{Reviewed by Cursor Bugbot for commit 15d1c59. Configure here.}