X Search MCP Server
Related Servers
Alternatives to X Search MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceSearch X (formerly Twitter) in real-time from your AI assistant using xAI's Grok API, with no X API account required.22 npmMIT
- AlicenseAqualityDmaintenanceEnables real-time search of X.com (Twitter) posts, users, threads, and trends via xAI's Grok API, directly from Claude.53MIT
- FlicenseAqualityCmaintenanceEnables searching X (Twitter) using the xAI Grok API to get summarised answers with citations. Supports filtering by handles, date range, and image/video understanding.12-
- 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 gradedqualityDmaintenanceEnables real-time web and Twitter/X search via Grok, returning structured results with source URLs, confidence scores, and key points. Supports multiple output modes, language options, and time range filtering.22 npm4MIT
- AlicenseAqualityAmaintenanceEnables 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.1118 npmMIT
TDQS
Scored across 3 tools
search_x and search_web_via_grok clearly target distinct sources, but search_combined is a superset of both, so an agent may reasonably wonder why it would ever pick the narrower tools. The descriptions do clarify intent, keeping them mostly distinguishable.
All three share the search_ prefix, which is good, but the suffixes vary in style (search_x, search_web_via_grok, search_combined) rather than following one predictable pattern. Still readable and mostly consistent.
Three tools is on the thin side for a search server, and one of them (search_combined) arguably subsumes the other two, making the surface feel slightly redundant rather than lean.
The core search domain is covered across X, web, and combined sources, but finer operations like thread retrieval, user/timeline lookup, or pagination are absent. Minor gaps an agent can work around.