x-mcp
Related Servers
Alternatives to x-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP agents to perform native X (Twitter) searches with original-post citations and transparent usage tracking. Supports existing Grok login sessions or explicit xAI API billing without runtime dependencies.17 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to search live public X/Twitter posts and fetch recent posts from user profiles without API keys, using zero-configuration local MCP tools for Claude, Cursor, and Pi.7 npm1MIT
- AlicenseNot gradedqualityDmaintenanceProvides programmatic X (Twitter) engagement via MCP, offering 24 tools for search, timelines, notifications, bookmarks, profiles, and tweet actions through a headless browser.MIT
- AlicenseBqualityDmaintenanceEnables searching X (formerly Twitter) using xAI's Responses API with support for filtering by handles, date ranges, and media understanding, returning structured results with citations.117 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables real-time search of X (Twitter) posts, user timelines, and trends using either xAI's Responses API or the official X API v2.4-
- AlicenseNot gradedqualityBmaintenanceLive X (Twitter) and web search for any coding agent through your existing Grok subscription. Exposes a grok_search MCP tool, so no X API key or X developer account is needed.20 npm30Apache 2.0
TDQS
Scored across 3 tools
The three tools occupy distinct roles in a pipeline: plan generation (x_search_topic), post ingestion (x_collect_posts), and config reporting (x_get_status). Boundaries are clear from descriptions, though the 'search' name on x_search_topic is slightly misleading since it returns a plan rather than results, which could momentarily confuse an agent about where actual data comes from.
All tools use a uniform x_verb_noun pattern (x_search_topic, x_collect_posts, x_get_status), with consistent prefixing and snake_case throughout. There are no deviations or mixed conventions.
Three tools is compact but matches the narrow, deliberately minimal harness workflow of plan→capture→status. Each tool earns its place, though the surface is on the lean side with no room for auxiliary operations.
The plan→collect→status lifecycle is closed, but the actual fetching is delegated entirely to the agent's external browser, so the server cannot complete a research task on its own. There is no post detail retrieval, refresh/clear operation, or recovery path if collection fails, leaving notable gaps for the stated research purpose.