# X MCP (slim)

> X MCP is X Corp.'s hosted Model Context Protocol server for the X API at api.x.com/mcp. It lets a model search posts, look up users, manage bookmarks, read trends and news, and draft Articles.

- Full: https://www.anchorterminal.com/tools/x-mcp.md (~7,400 tokens) · this version ~1,480 tokens · JSON https://www.anchorterminal.com/tools/x-mcp.json · canonical https://www.anchorterminal.com/tools/x-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-08

**C · 55.4/100 · rank #451 of 629 · #6 in Social media posting APIs · not agent-ready · confidence medium**


Assessment: First-party access to full-archive post search, user lookup, trends and news, with OAuth 2.0 PKCE scopes and per-resource prices published without a login. Every user must create a paid X developer app, the tool list isn't published, and the documented tools don't create posts.

## Facts

- Kind: MCP server · vendor: X Corp. · category: Social media posting APIs · legal entity: X Corp. · provenance 89/100
- Endpoint: `https://api.x.com/mcp` (Streamable HTTP, stdio)
- Auth: OAuth or key · pricing: Pay per use · x402: no · licence: Proprietary hosted server under the X Developer Agreement. The xurl bridge on GitHub and npm is MIT
- Probe metrics: not measured yet (probes haven't run)
- Server: Hosted Streamable HTTP at https://api.x.com/mcp, protocol 2025-06-18, serverInfo `xmcp`. Closed source
- Tools: Posts (lookup, likers, reposters, quoters, counts), full-archive post search, user search, news search, user lookup and timelines, bookmarks and folders, trends by location, Article drafts and publishing. The tool count isn't published
- Not covered: Creating posts or replies, likes, follows and direct messages aren't in the documented tool groups
- Access: Own X developer app on Pay-per-use in Production. App-only Bearer token for reads, or OAuth 2.0 PKCE through the `xurl mcp` bridge for user context
- Bridge: @xdevplatform/xurl 1.3.4 (MIT, Go, 29 September 2026), run with npx. Tokens cached in ~/.xurl
- Pricing: Prepaid credits. $0.005 a post read, $0.010 a user read, $0.001 an owned read, $0.005 a bookmark write, capped at 3 million post reads a month on Pay-per-use
- Rate limits: Per endpoint and 15-minute window on the API, such as 300 per 15 minutes and 1 a second for full-archive search and 50 per 15 minutes for bookmark writes. No MCP-specific limits published
- Docs for agents: llms.txt, llms-full.txt, Markdown for every page, skill.md, AGENTS.md and an OpenAPI spec at https://api.x.com/2/openapi.json
- Prices: Post read $0.005 per record; User read $0.01 per record; Owned read (the app owner's own posts, bookmarks, followers) $0.001 per record; Bookmark write $0.005 per call; Trends request $0.01 per call

- Scores: Reliability 72, Performance pending, Schema & documentation 65, Agent ergonomics 45, Security & auth 48, Payments & pricing 20, Task success pending, Maintenance & community 70, Transparency & trust 70 · total over the 7 assessed categories
- Why: Reliability, Read with the hosted lines, since the server runs at api.x.com and the bridge only relays. · Schema & documentation, A public OpenAPI spec covers the API behind it (version 2.169, 175 paths, 218 operations). · Agent ergonomics, The number of tools isn't published. · Security & auth, OAuth 2.0 authorisation code with PKCE (S256), scopes and refresh tokens, and the resource metadata accepts bearer tokens in the header only… · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, The xurl bridge reached 1.3.4 on 29 September 2026 and the platform changelog's latest entry is 2 October 2026 (30). · Transparency & trust, The hosted server is closed, under a Developer Agreement last updated 27 April 2026, and the bridge is MIT (18 of 30).
- Sources: 24, open questions: 11, both in the full twin
- Capabilities: social.analytics
- JSON: https://www.anchorterminal.com/api/v1/tools/x-mcp.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/x-mcp.svg` or a link to https://www.anchorterminal.com/tools/x-mcp from a page on docs.x.com or one of its subdomains, or the README of github.com/xdevplatform/xurl, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Use the app-only Bearer header for read-only work. Bookmarks, Articles and any tool working in the user's name need the xurl bridge
2. Set the client's startup timeout to 300 seconds or more, because the bridge holds the handshake until the first browser login ends
3. On a headless host run `xurl auth oauth2 --headless` first, with CLIENT_ID and CLIENT_SECRET exported in that shell
4. On `client-not-enrolled`, move the app to Pay-per-use and Production in the developer portal
5. On 429, wait until the Unix time in `x-rate-limit-reset`. No Retry-After header is documented

## Connect

```bash
npm install -g @xdevplatform/xurl
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/x-mcp

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Zernio (formerly Late) API + MCP | B | 67.5 | social.analytics | https://www.anchorterminal.com/tools/late.min.md |
| Buffer API + MCP | B | 62 | social.analytics | https://www.anchorterminal.com/tools/buffer.min.md |
| Postiz API + MCP | C | 59.3 | social.analytics | https://www.anchorterminal.com/tools/postiz.min.md |
| Upload-Post API + MCP | C | 58.7 | social.analytics | https://www.anchorterminal.com/tools/upload-post.min.md |
| Ayrshare API + MCP | C | 57.2 | social.analytics | https://www.anchorterminal.com/tools/ayrshare.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)