X’s official MCP still leaves API cost and auth work to handle
X’s official MCP takes more setup than a simple plug-in connection for AI agents. Even read-only use, such as searching posts, still requires an X developer app and managed .
The does not add its own extra fee, but each request to X still counts against the user’s X API plan. Agents that publish often can hit limits quickly, so retry logic with is needed.
OAuth setup has several parts that must match, including the client ID, client secret, redirect URI, and bridge. Personal data such as bookmarks or a timeline cannot be accessed with an app-only token, so full user OAuth is required.
Key points
- Read-only use still needs an X developer app and .
- The itself does not add a fee, but X API calls still count against the API plan.
- Agents that post often need retry logic and .
- OAuth setup depends on several matching values before requests work.
- Bookmarks and timelines need user OAuth, not just an app-only token.