X WebMCP

Use this skill to operate X through the built-in --site x bridge preset in @webmcp-bridge/local-mcp.

For generic bridge setup patterns or non-X sites, switch to $webmcp-bridge.

Prerequisites

• - uxc is installed and available in PATH.
• INLINECODE5 is installed and available in PATH.
• Network access to https://x.com.
• On a fresh machine, or under an isolated HOME, install Playwright browsers first with npx playwright install.
• X is auth-sensitive. Expect bootstrap_then_attach behavior when the profile is not signed in yet.

Core Workflow

1. 1. Ensure the fixed X link exists:

1. 2. Inspect the bridge and tool schema before calling tools:

1. 3. Check authentication state first when the profile is new or looks stale:

1. 4. Use read tools for timelines, conversations, and profiles:

1. 5. Use write tools only after reading help and confirming user intent:

1. 6. Use Grok through the same authenticated X session:

1. 7. Parse JSON output only:

Default Target

The built-in preset uses:

CODEBLOCK0

The default profile path is:

CODEBLOCK1

Refresh the link with:

CODEBLOCK2

Guardrails

• - Keep the X profile isolated from other sites.
• X uses bootstrap_then_attach; do not expect page tools to work until the managed profile is authenticated.
• Prefer explicit bridge.session.mode.set over relaunching the command to change runtime mode.
• INLINECODE39 and article publishing can take a long time. Increase timeoutMs instead of retrying aggressively.
• For local uploads such as attachmentPaths, markdownPath, or coverImagePath, always use absolute filesystem paths.
• Use dryRun for destructive or public write tools first when available.
• If the user closes the visible X window manually, the headed owner session ends. Run x-webmcp-cli bridge.open again if you still need a visible session on the same profile.

References

• - Common command patterns:

• - Link creation helper: