PageIndex MCP server

• Addresshttps://mcp.pageindex.ai/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on pageindex.ai when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

• Stateanswerschecked 2026-10-27
• Tools10
• Server calls itselfpageindex-chat
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 213 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer833 ms
• Space in an agent's context≈ 6,219 tokensthe definitions of all its tools (10), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• browse_documents

  Primary document retrieval tool. After orienting with `get_folder_structure()` (when available) — and, for queries that may involve typed attributes, pairing it with `get_metadata_schema()` so you know which fields metadata mode could…

• search_documents

  Escalation tool — never the first discovery step. Always start with `browse_documents()` (after `get_folder_structure()` when visible). Pick a mode: • mode="query" — keyword precision when browse missed a known doc by precise term…

• get_folder_structure

  Orientation step: show the folder hierarchy as a tree (like `tree -d`). **Call this before browse_documents()** to plan targeted retrieval — folder names reveal content domains (e.g. "Research", "Finance") and return folder IDs you pass…

• get_metadata_schema

  List declared metadata fields (names, types, descriptions) so you can build `metadata_filter` / `sort` / `aggregates` / `group_by` for `search_documents(mode="metadata")`, or a `metadata_filter` that narrows `mode="query"`. Call it only…

• get_document

  Check a document's processing status and metadata. Call this before `get_document_structure()` or `get_page_content()` to confirm the document is ready (`status === "completed"`).

• get_document_structure

  Extract a document's hierarchical outline (headers, sections, page references). REQUIRED for documents over 20 pages — call this first to locate relevant sections, then pass their page numbers to `get_page_content()`. Use the `part`…

• get_page_content

  Extract page content from a processed document. Use tight, targeted page ranges — never the whole document at once. For documents over 20 pages, call `get_document_structure()` first to pick relevant sections. Embedded image paths in the…

• get_document_image

  Retrieve an image from a document — pass an `image_path` from a `get_page_content()` response: either an embedded image (from a content block) or a full rendered page (from the `page_images` array, useful when a page is scanned or its…

• remove_document

  Permanently delete documents and all associated data. Only invoke when the user explicitly names the documents AND confirms deletion. Returns `results` — one entry per requested document: `{ doc_name, status: "deleted" | "not_found" |…

• process_document

  Upload and process a PDF from a public URL (≤100MB). Only invoke with a valid URL the user has provided — never guess one. After processing, call `get_document()` to confirm status before reading content.