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
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to navigate long PDFs by address—sections, pages, tables, figures, notes, and terms—so they can read selectively and cite the PDF page behind each answer.12MIT
- AlicenseAqualityDmaintenanceEnables any LLM to process arbitrarily long contexts through recursive decomposition, without requiring external LLM APIs.1720 npm15MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.36AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables querying Confluence documents through agentic reasoning over hierarchical document trees, replacing vector similarity with structural navigation.Apache 2.0
- AlicenseAqualityDmaintenanceEnables 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.716ISC
TDQS
Scored across 10 tools
Most tools target distinct operations: processing, status, structure, page content, images, deletion, metadata schema, and folder orientation. The main overlap is browse_documents vs. search_documents, but their descriptions establish a clear primary/escalation workflow, reducing practical confusion.
All tool names use snake_case and follow a predictable verb_noun pattern such as process_document, get_document_structure, get_page_content, and remove_document. Pluralization on collection-oriented tools like browse_documents and search_documents is consistent and readable.
Ten tools is well-scoped for a document-processing and retrieval server. Each tool covers a distinct part of the lifecycle, from ingestion and discovery to structure extraction, page access, images, metadata, and deletion.
The surface covers core document lifecycle operations: processing, browsing, searching, metadata inspection, structure/content/image retrieval, folder orientation, and deletion. Minor gaps remain around document or folder updates, moves, renames, or metadata edits, which agents may need for full library management.