Grokipedia MCP Server
Related Servers
Alternatives to Grokipedia MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables searching and retrieving articles, citations, and structured content from Grokipedia for research and information retrieval. It provides specialized tools for section extraction, related page discovery, and filtered search results.7MIT
- AlicenseAqualityDmaintenanceEnables searching and retrieving content from Grokipedia, with tools for page lookup, citations, sections, and related pages.7MIT
- AlicenseAqualityDmaintenanceEnables searching X (Twitter) posts, discussions, trends, and web content via Grok API using natural language.311 npm1MIT
- AlicenseBqualityDmaintenanceProvides comprehensive web, news, and Twitter search capabilities using the xAI Grok API with both basic and deep analysis modes. It includes advanced features like timeline generation, sentiment analysis, and built-in reliability through caching and retry logic.517 npm19MIT
- FlicenseNot gradedqualityDmaintenanceEnables searching and retrieving Wikipedia content across multiple languages, including article summaries, sections, coordinates, and related topics.-
- AlicenseAqualityDmaintenanceEnables real-time search of X.com (Twitter) posts, users, threads, and trends via xAI's Grok API, directly from Claude.53MIT
TDQS
Scored across 7 tools
Most tools are clearly distinct: search finds articles, get_page retrieves metadata, get_page_content isolates body text, get_page_citations returns references, and get_page_sections lists headers. However, get_page and get_page_content could be confused since both return article content, though the descriptions clarify that get_page includes metadata and citations while get_page_content is content-only.
Tool names mostly follow a consistent verb_noun pattern: get_page, get_page_content, get_page_citations, get_page_sections, get_linked_pages, search. The only deviation is 'search' lacking a noun (e.g., search_pages), but it is still readable and predictable.
Seven tools is well-scoped for a wiki/knowledge-base server. Each tool covers a distinct retrieval need: search, page metadata, content, citations, sections, section detail, and linked pages. No redundant or unnecessary tools.
The server covers the main read-only retrieval workflows for a wiki: search, get page, get content, get citations, get sections, and get linked pages. Minor gaps include no way to get a page's full raw markdown in one call (content preview only) and no direct page history or related-pages API, but agents can work around these with existing tools.