x-mcp-server
Related Servers
Alternatives to x-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that provides AI agents with full access to the X (Twitter) API for posting, searching, and managing engagement through natural language. It supports comprehensive tools for tweet management, media uploads, and account analytics across multiple MCP-compatible clients.1560MIT
- AlicenseAqualityBmaintenanceMCP server for the Twitter/X API, enabling search, user profiles, tweets, followers, and more via natural language.941,043 npm6MIT
- AlicenseAqualityCmaintenanceMCP server for Twitter/X enabling AI agents to search, post, reply, and engage with tweets.147 npm2MIT

X API FastMCP Serverofficial
FlicenseNot gradedqualityDmaintenanceA local MCP server that exposes the X API (formerly Twitter API) as tools, enabling operations like posting, searching, user management, and more via natural language commands.867-- AlicenseNot gradedqualityBmaintenanceThis MCP server lets an assistant operate your own X account — posting, threads, media, timelines, search, DMs, bookmarks, lists, trends, analytics, and profile actions — exposing one tool per operation plus meta-tools for schema search and validated invocation. It uses the official X API for 49 operations and keeps 11 unofficial browser-session actions such as likes, follows, and profile edits off by default, available only after explicit opt-in with cookies and a risk acknowledgment.Apache 2.0
- AlicenseAqualityCmaintenanceExposes the Twitter/X API as native MCP tools, letting agents search tweets and users, pull profiles, timelines, followers, lists, communities, and trends, and read account-scoped data like bookmarks, DMs, and home timeline. It also performs write actions such as posting, liking, retweeting, following, and their reversals, using an API key with optional linked or per-call X account credentials.991,043 npmMIT
TDQS
Scored across 8 tools
Tools have largely distinct purposes: get_active_account (local config) vs get_me (authenticated API user) vs get_user (by username) are differentiated by descriptions, and get_post vs get_user_posts vs search_posts are clearly separated. Minor potential confusion among the three user-retrieval tools, but descriptions resolve it adequately.
All tools follow a consistent snake_case pattern with an x_ prefix and verb_noun structure (e.g., x_get_user, x_create_post, x_reply_post). No deviations in style or convention.
Eight tools is well-scoped for a focused X API server covering basic read and write operations. Each tool earns its place, with no redundant or excessive entries.
The surface covers reading posts/users and creating posts/replies, but notable gaps exist: no delete or edit post, no like/retweet, and no follow/unfollow. These missing operations limit common agent workflows.