X Use
Related Servers
Alternatives to X Use
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides read-only access to public X (Twitter) data, including profiles, tweets, timelines, threads, followers, and search, for developers and AI agents.1MIT

@xcrap/mcpofficial
AlicenseAqualityCmaintenanceProvides read-only access to X (Twitter) data — posts, threads, profiles, timelines, followers, media, and trends — through twelve tools, with no login or API key required.1220 npm1MIT- AlicenseNot gradedqualityBmaintenanceEnables read-only access to X API v2 through MCP tools, returning capped results with release metadata on every response.Apache 2.0
- AlicenseAqualityCmaintenanceEnables read-only research on public X data through tools for posts, threads, profiles, search, trends, collections, and saved-result analysis using free public APIs and optional sessions.8MIT
- AlicenseBqualityBmaintenanceEnables read-only access to X/Twitter for searching posts, viewing profiles, timelines, threads, and trending topics without posting, liking, reposting, or sending direct messages.7MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to interact with the X (Twitter) API v2 through 41 typed tools for reading, searching, engaging, publishing, and managing content, with policy-based access control and session credit budgets to prevent overspending.4149 npm1MIT
TDQS
Scored across 7 tools
Each tool maps to a fairly distinct target: search, single post, user lookup, user timeline, media, thread, and status. The only mild overlaps are x_post vs x_thread (both return posts) and x_search vs x_user_posts (both return post collections), but the descriptions make the boundaries clear.
All tools use a consistent 'x_' prefix with snake_case, keeping them visually grouped and predictable. The only wrinkle is that x_post is a noun-style name that could be misread as a write action, though 'Read-only' in the description resolves it.
Seven tools is a tight, well-scoped set for an X read client, with no redundant entries. Every tool covers a distinct resource path (search, post, user, timeline, media, thread, diagnostics).
Read coverage is solid across posts, users, timelines, threads, and media, plus an auth/credit diagnostic. However, the surface is entirely read-only with no write operations (post, reply, like, repost, follow), and common reads like followers/following lists or engagement metrics are absent, which will limit many agent workflows.