SOCIAL MEDIA / X
X MCP Server
X's official hosted MCP server at api.x.com/mcp exposes full-archive post search, user lookup, bookmarks, trends, news and Article drafting over Streamable HTTP. Because X has no dynamic client registration, the publisher ships the open-source xurl bridge (npm @xdevplatform/xurl, Go, MIT) that owns the app identity, performs the one-time OAuth 2.0 PKCE browser login and injects a fresh Bearer token on every call. A second hosted server at docs.x.com/mcp serves the X API documentation.
“The X API exposes a hosted Streamable HTTP MCP server at https://api.x.com/mcp (protocol 2025-06-18, serverInfo: xmcp).”
01 / THE REASONING
Why this made the selection.
- X documents a hosted Streamable HTTP MCP server at https://api.x.com/mcp on its own developer docs, with a capability table for posts, search, users, bookmarks, news and trends, and Articles, plus a separate docs-search server at https://docs.x.com/mcp.
- Because X has no dynamic client registration, the publisher ships the open-source xurl bridge (MIT, Go) that owns the app identity, performs the OAuth 2.0 PKCE login and refreshes tokens in-process; the README at the pin documents xurl mcp as a stdio-to-Streamable-HTTP relay.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- X developer docs MCP page: two hosted servers — the X API MCP at https://api.x.com/mcp (Streamable HTTP, protocol 2025-06-18, serverInfo xmcp) and the Docs MCP at https://docs.x.com/mcp; capability table covering posts, full-archive search, users, bookmarks, news and trends, and Articles; OAuth requires your own developer app with no dynamic client registration; the xurl bridge handles login and token refresh; an app-only Bearer route exists for read-only access.
- xurl repository at pinned revision 18dcb447f090667171ff23666a05d6d387e2aa73: README documents `xurl mcp` as a stdio JSON-RPC bridge that relays each message to the remote Streamable HTTP endpoint with a fresh Bearer token, holds the MCP session id, refreshes the token in-process, opens the browser for the one-time OAuth 2.0 login and writes diagnostics to stderr so stdout stays a clean JSON-RPC channel; go.mod declares module github.com/xdevplatform/xurl (go 1.24.2); LICENSE is MIT.
- docs.x.com/tools/mcp re-read on 2026-10-13 as markdown (https://docs.x.com/tools/mcp.md); xurl README.md, go.mod and LICENSE re-read at the pin.
Our findings
- The hosted server is the only execution surface; the bridge is the only local component and carries the MIT licence.
- Writes — bookmarks and Articles — require the user-context OAuth route; the app-only Bearer route is read-only.
- The xurl LICENSE at the pin is MIT, Copyright (c) 2024 Santiago Medina Rolong; the repository sits in the xdevplatform organisation.
- Upstream health on 2026-10-13: the docs page still states the endpoint, protocol 2025-06-18, the bridge command and the Cursor block used as configExample; xdevplatform/xurl is not archived, its default-branch HEAD is the pin, and npm/package.json there names @xdevplatform/xurl with licence MIT.
Not established by this review
- No X developer app was created; no post was fetched, searched or drafted.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
npx -y @xdevplatform/xurl mcp https://api.x.com/mcp Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- Create an X app with OAuth 2.0 enabled in the Developer Portal and register the redirect URI http://localhost:8080/callback.
- Add the configExample to the MCP client with the app's CLIENT_ID and CLIENT_SECRET.
- Complete the one-time browser login on first run; the bridge caches and auto-refreshes the token thereafter.
Before you start
- An X developer app with OAuth 2.0 enabled.
- API credits in the X Developer Console for billable reads and writes.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"xapi": {
"command": "npx",
"args": [
"-y",
"@xdevplatform/xurl",
"mcp",
"https://api.x.com/mcp"
],
"env": {
"CLIENT_ID": "YOUR_X_APP_CLIENT_ID",
"CLIENT_SECRET": "YOUR_X_APP_CLIENT_SECRET"
}
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://docs.x.com/tools/mcp
Supports: summary, upstreamDescription, homepage, descriptionSourceUrl, install, configExample, compatibility, access, limitations, transports, whySelected
https://github.com/xdevplatform/xurl/blob/18dcb447f090667171ff23666a05d6d387e2aa73/README.md
Supports: repository, revision, whySelected, review
https://github.com/xdevplatform/xurl/blob/18dcb447f090667171ff23666a05d6d387e2aa73/go.mod
Supports: language
https://github.com/xdevplatform/xurl/blob/18dcb447f090667171ff23666a05d6d387e2aa73/LICENSE
Supports: license