X's Hosted MCP Server: Live-Data Access for AI Agents Explained

Key Takeaways

• What MCP is: the Model Context Protocol is a universal "plug" — instead of custom wiring per app, any AI tool talks to any service the same way. One shape, one socket.
• What X shipped (June 30, 2026): a hosted MCP server at api.x.com/mcp. Before this you had to stand up your own server, wire the X API by hand, and keep it running. Now X hosts the bridge — you just connect with your own X account.
• A second docs server at docs.x.com/mcp lets your agent read X's own developer documentation on the fly, so it can look up how things work while you build.
• Read-only, not a megaphone: the hosted setup is built for reading and pulling data — searching posts, users, conversations, trends, and bookmarks — not for auto-posting on your behalf. Treat it as your agent's live research window into X.
• Auth model: connection uses OAuth — you log in with your own X account and grant scoped, revocable permission (never your password). A small open-source helper called xurl runs locally, holds your tokens, and auto-refreshes them so you're not constantly logging back in.
• Getting-started flow: (1) create a free X developer app, (2) enable OAuth for it, (3) install and configure xurl, (4) point your AI client at the X MCP server address, (5) enable only the specific tools you need.
• The #1 setup mistake: turning on all 200+ tools at once overwhelms the agent and it can't decide which to use. Start with just Search and User Lookup, then add more as you actually need them.
• Security hygiene: treat your tokens like private keys — never paste them into a chat or drop them into shared files. And point your agent at the docs server too, not just the main one, to cut back-and-forth.