X MCP

X's official hosted MCP surface: one endpoint for X API actions and one endpoint for X documentation. Use it as source authority before extending older local xmcp assumptions.

Current Source

The official docs expose two hosted MCP servers:

The API endpoint reports protocol 2025-06-18 and serverInfo: xmcp. App-only bearer tokens can cover read-only access where allowed. User-context or write flows require the xurl mcp local bridge, which handles OAuth 2.0 PKCE and injects fresh bearer tokens. Source: X MCP docs, checked 2026-07-06

Local Route

Route X-data tasks through X-Agent first. X MCP updates the source boundary:

• check official Docs MCP and X MCP docs before building local wrappers;
• keep user-context OAuth in the xurl mcp bridge rather than in prompts;
• separate read-only source gathering from write or account-scoped actions;
• log which MCP server and auth mode supplied each result.

For bookmark ingestion, this matters because X search/bookmarks are now first-party agent tools. The wiki should still preserve enriched JSON and local media artifacts so downstream pages do not depend on live X availability.

Timeline

• 2026-07-06 | Page created from the July X bookmark batch and official docs. Local decision: treat hosted X MCP + Docs MCP + xurl mcp as the current X agent surface; preserve the older X-Agent cost/read-write split. Source: X docs, 2026-07-06