Grokipedia MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search Grokipedia (AI-curated knowledge base) for articles. Use for: finding Grok-generated articles, discovering AI-synthesized knowledge, research. Returns: title, slug (for get_page), snippet, relevance score, view count. Tips: Use the slug from results with get_page/get_page_content for full articles. |
| get_pageA | Get complete Grokipedia page with metadata, content preview, and citations. Use for: reading articles, getting overviews, checking citations and sources. Returns: title, description, content preview (truncated), citations list. Tips: Use get_page_content for full untruncated content. Slug comes from search results. |
| get_page_contentA | Get full article content from Grokipedia (larger than get_page preview). Use for: reading complete articles, comprehensive research, when you need all content. Returns: title, full content (up to max_length), content_length. Tips: Set max_length higher for very long articles. Returns raw markdown. |
| get_page_citationsA | Get the source citations for a Grokipedia article. Use for: finding source materials, verifying claims, academic research, fact-checking. Returns: list of citations with title, URL, and description. Tips: Great for grounding AI-generated knowledge with original sources. |
| get_related_pagesA | Discover related Grokipedia pages linked from an article. Use for: exploring connected topics, building knowledge graphs, follow-up research. Returns: list of related pages with titles and slugs. Tips: Use returned slugs with get_page to dive into related topics. |
| get_page_sectionA | Extract a specific section from a Grokipedia article by header name. Use for: focusing on particular aspects of a topic (e.g., 'History', 'Applications'). Returns: section header and content. Tips: Use get_page_sections first to discover available section headers. |
| get_page_sectionsA | Get the table of contents (all section headers) for a Grokipedia article. Use for: understanding article structure, finding which sections exist. Returns: list of sections with level (1=H1, 2=H2, etc.) and header text. Tips: Call before get_page_section to find valid section headers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| research_topic | Research a topic by searching and retrieving detailed information |
| find_sources | Find authoritative sources and citations for a topic |
| explore_related | Explore topics related to a specific article |
| compare_topics | Compare two topics side by side |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Tools are mostly distinct with clear purposes, though `get_page` overlaps functionally with `get_page_content` (preview vs full) and `get_page_citations` by including citations in its response. Descriptions clarify these distinctions, but an agent might initially hesitate between the general getter and specialized ones.
Strong snake_case convention with consistent `get_page_*` pattern for article-specific operations. Minor deviations with `search` (lacks `get_` prefix) and `get_related_pages` (uses `related` instead of `page_related`), but overall readable and predictable.
Seven tools is well-scoped for a read-only encyclopedia server. The set efficiently covers discovery (search), retrieval granularity (full page, content only, section only, sections list), verification (citations), and navigation (related pages) without bloat.
Comprehensive coverage for accessing Grokipedia articles with good traversal support (search → get → related). Minor gap: no dedicated metadata-only endpoint (though `get_page` provides it alongside preview content). No write operations, which appears intentional for this domain.