PageIndex MCP
Related Servers
Alternatives to PageIndex MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to accurately navigate and retrieve information from complex documents using Page Index RAG methodology.4MIT
- AlicenseAqualityDmaintenanceEnables any LLM to process arbitrarily long contexts through recursive decomposition, without requiring external LLM APIs.176 npm15MIT
- AlicenseNot gradedqualityAmaintenanceEnables vectorless RAG by letting LLM clients like Claude and Cursor parse documents, inspect outlines, and retrieve specific sections with heading breadcrumbs. Supports PDF, Word, HTML, and PowerPoint without LLM calls or heavy ML models.35AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables querying Confluence documents through agentic reasoning over hierarchical document trees, replacing vector similarity with structural navigation.Apache 2.0
- FlicenseAqualityCmaintenanceEnables AI agents to efficiently process large local and online PDFs through selective extraction of text, images, and metadata. It provides tools for content search and document outline navigation to optimize context window usage.715-
- AlicenseAqualityAmaintenanceEnables AI agents to read and analyze PDF documents for natural language Q\&A. Supports multiple LLM providers including Google Gemini, Anthropic Claude, and OpenAI.130 npm4Apache 2.0
TDQS
Scored across 9 tools
Each tool has a distinct role in the document lifecycle, and overlapping discovery tools (browse vs. search) are explicitly differentiated. However, get_folder_structure vs. get_document_structure could momentarily confuse an agent despite their different targets.
All tools follow a consistent snake_case verb_noun pattern, with get_* used uniformly for retrieval-oriented operations and clear action verbs like process, remove, browse, and search. There are no mixed conventions or vague generic names.
Nine tools is well within the ideal range and each tool earns its place, covering ingestion, deletion, navigation, search, status checking, structure extraction, page content, and image retrieval without redundancy.
The tool surface covers the full document workflow: add/remove documents, browse/search the corpus, check processing status, navigate structure, extract page content, and retrieve images. There are no obvious dead ends or missing operations for the stated domain.