PageIndex MCP
A self-hosted MCP server for PageIndex's vectorless, reasoning-based document retrieval. It ingests PDFs into a hierarchical table of contents using an LLM and serves documents, structure, and page content via MCP tools.
README
PageIndex MCP (self-hosted)
A self-hosted MCP server exposing PageIndex's
vectorless, reasoning-based document retrieval. The pageindex/ directory is a
vendored copy of VectifyAI's open-source PageIndex package (MIT licensed, see
pageindex/LICENSE.upstream).
How it works:
- Ingest (
app/ingest.py): builds a hierarchical "table of contents" tree for a PDF using an LLM (Gemini Flash by default, configurable viaPAGEINDEX_MODEL/pageindex/config.yaml+ LiteLLM). This costs a small amount of LLM usage, once per document. - Hybrid OCR (
app/ocr.py): pages whose embedded text layer is too sparse (scans, image-heavy slides) are rendered and transcribed by a vision model during ingest; born-digital text pages are read losslessly for free. The transcriptions are cached so retrieval serves them too. Disable withPAGEINDEX_OCR_MODEL=off. - Serve (
app/server.py): exposeslist_documents,get_document,get_document_structure,get_page_contentas MCP tools over streamable HTTP, protected by a bearer token. The connecting agent (e.g. Claude) does the navigation/reasoning itself - serving is free after ingest. - Text files: anything that isn't a PDF (code, Jupyter notebooks,
markdown, any UTF-8 file up to 10 MB) is stored as plain text without LLM
ingest - instantly available, zero cost. The same MCP tools serve them,
with 1-indexed line numbers taking the role of page numbers (e.g.
get_page_content(doc_id, "1-200")returns the first 200 lines). Notebook outputs are stripped on upload; only markdown and code cells are kept. - Web UI (
/): minimal document manager - create folders (projects), upload PDFs and text files (PDF ingest runs in background workers), watch queued/processing status, rename and delete documents. Clicking a document opens a detail view (description, dates) with a button to open the original PDF/file in a new tab. Unlock with the same bearer token; it is kept in the browser's localStorage.
Setup
-
Copy
.env.exampleto.envand fill in:GEMINI_API_KEY- used only during ingest (tree building + OCR)PAGEINDEX_MCP_API_KEY- bearer token clients must send, e.g.openssl rand -hex 32- optional:
PAGEINDEX_MODEL(any LiteLLM model id for tree-building; default gemini/gemini-3.5-flash),PAGEINDEX_OCR_MODEL(vision model for text-poor pages, "off" to disable),PAGEINDEX_INGEST_WORKERS(parallel PDF ingests, default 2) andPAGEINDEX_MAX_CONCURRENT_LLM(global cap on simultaneous LLM calls, default 8 - protects against provider rate limits; if an ingest still hits a rate limit or the model is overloaded, it is re-queued automatically with a growing cooldown)
-
Build and start:
docker compose up -d --build -
Upload PDFs and text files via the web UI at
https://<your-domain>/(unlock with thePAGEINDEX_MCP_API_KEY). PDF ingest runs in the background; the list shows processing/done/failed per document. Text files are done immediately.Alternatively via CLI inside the container:
docker compose exec pageindex-mcp python3 app/ingest.py /data/pdfs/lecture01.pdf --project "Machine Learning"Trees are saved to
<data>/trees/<doc_id>.jsonand registered in<data>/documents.json.
Connecting an MCP client
{
"mcpServers": {
"pageindex-self": {
"type": "http",
"url": "https://<your-domain>/mcp",
"headers": {
"Authorization": "Bearer <PAGEINDEX_MCP_API_KEY>"
}
}
}
}
For Claude Code:
claude mcp add --transport http pageindex-self https://<your-domain>/mcp \
--header "Authorization: Bearer <PAGEINDEX_MCP_API_KEY>"
For opencode (~/.config/opencode/opencode.json, or a project-level
opencode.json):
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pageindex-self": {
"type": "remote",
"url": "https://<your-domain>/mcp",
"enabled": true,
"headers": {
"Authorization": "Bearer <PAGEINDEX_MCP_API_KEY>"
}
}
}
}
To keep the token out of the config file, opencode supports env substitution:
"Authorization": "Bearer {env:PAGEINDEX_MCP_API_KEY}".
Deployment
The compose file attaches the service to the external dokploy-network, so in
Dokploy you only need to add a domain pointing at service pageindex-mcp,
port 8000 (Traefik handles TLS). The container port is intentionally not
published on the host - the bearer token must only travel over HTTPS.
For plain local use (no Dokploy), swap the networks section for the
commented-out 127.0.0.1 port binding in docker-compose.yml.
GET /health is unauthenticated and returns ok - useful for uptime checks.
Persistence
../files/data/ (PDFs, generated trees, registry) is bind-mounted and persists
across rebuilds/restarts. On Dokploy this is the app's files storage dir,
which survives redeploys (the code dir does not). Back it up if you don't want
to re-run ingest.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。