MCP PDF to PGVector
MCP server that ingests PDF documents into pgvector for semantic search and RAG pipelines. It handles extraction, chunking, local embeddings, and storage, enabling agents to make PDFs searchable via natural language.
README
<p align="center"> <img alt="Python" src="https://img.shields.io/badge/python-3.10+-blue.svg"> <img alt="License" src="https://img.shields.io/badge/license-MIT-green.svg"> <img alt="MCP" src="https://img.shields.io/badge/MCP-1.28.1-purple.svg"> <img alt="pgvector" src="https://img.shields.io/badge/pgvector-0.8+-orange.svg"> <img alt="Status" src="https://img.shields.io/badge/status-production%20ready-brightgreen.svg"> </p>
<h1 align="center">MCP PDF to PGVector</h1>
<p align="center"> An MCP server that ingests PDF documents into pgvector for semantic search and RAG pipelines. <br> The ingestion half of a production RAG system — extract, chunk, embed, and store. </p>
<hr>
Problem
Large language models have no direct access to documents, PDFs, or private knowledge bases. Building a RAG pipeline requires stitching together PDF parsing, text chunking, embedding generation, and vector database operations — a fragile, multi-step process that every agent project reinvents.
This MCP server collapses that pipeline into a single agent-callable tool: point it at a directory of PDFs, and it handles extraction, chunking, embedding (nomic-embed-text-v2-moe, 768-dim), and storage in pgvector — ready for semantic search.
Features
- Single
uv runorpip install— no project scaffolding, no boilerplate. - Local embeddings — nomic-embed-text-v2-moe runs on CPU via sentence-transformers, no API keys or network calls.
- Background ingestion —
index_pdfs_for_ragreturns immediately; pollcheck_indexing_progressfor updates. - Idempotent resume — re-running indexes only new/changed files (SHA-256 content hash).
- Per-file error isolation — one corrupt PDF never blocks the batch.
- Auto HNSW index — pgvector index created after ingestion for sub-10ms similarity search.
- Production stable — uses
mcp==1.28.1(stable SDK), no pre-releases.
Architecture
┌────────────────────────────────────────────────────────────┐
│ Agent (OpenCode, Claude Desktop, etc.) │
│ calls index_pdfs_for_rag(pdf_directory, collection_name) │
└─────────────────────┬──────────────────────────────────────┘
│ JSON-RPC (stdio)
┌─────────────────────▼──────────────────────────────────────┐
│ server.py — MCP Server (FastMCP v1) │
│ │
│ 1. Scan PDF directory (recursive glob) │
│ 2. Compute SHA-256 hash of each file │
│ 3. Extract text (PyMuPDF) │
│ 4. Recursive character chunking (1000/200 default) │
│ 5. Batch embed (nomic-embed-text-v2-moe, 768-dim) │
│ 6. Batch insert into pgvector (ON CONFLICT DO NOTHING) │
│ 7. Create HNSW index on completion │
└─────────────────────┬──────────────────────────────────────┘
│ asyncpg
┌─────────────────────▼──────────────────────────────────────┐
│ PostgreSQL + pgvector │
│ │
│ documents ( │
│ collection_name TEXT, ← namespace for multi-tenant │
│ file_hash TEXT, ← SHA-256 for resume/dedup │
│ file_path TEXT, ← original source │
│ chunk_index INT, ← position within file │
│ content TEXT, ← chunk text │
│ embedding vector(768), ← nomic embedding │
│ metadata JSONB, ← extensible │
│ UNIQUE(collection_name, file_hash, chunk_index) │
│ ) │
└────────────────────────────────────────────────────────────┘
Quick Start — Agent (OpenCode)
Add to your opencode.json or ~/.config/opencode/opencode.json:
{
"mcp": {
"mcp-pdf-to-pgvector": {
"type": "local",
"command": ["/path/to/mcp-pdf-to-pgvector/.venv/bin/python", "server.py"],
"enabled": true
}
}
}
Once configured, the agent can call:
index_pdfs_for_rag(
pdf_directory="/path/to/pdfs",
collection_name="company-policies"
)
Then poll progress:
check_indexing_progress(task_id="...")
Quick Start — Local Testing
Prerequisites
- Python 3.10+
- PostgreSQL 15+ with pgvector extension
Setup
# Clone and enter
git clone <url>
cd mcp-pdf-to-pgvector
# Create virtual environment and install dependencies
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
# Configure pgvector connection
cp .env.example .env
# Edit .env with your pgvector credentials
# Start the server (listens on stdio)
python server.py
Test with MCP Inspector
source .venv/bin/activate
mcp dev server.py
Opens a browser UI where you can call index_pdfs_for_rag with a PDF directory path and collection name, then monitor progress with check_indexing_progress.
Configuration
All configuration is via environment variables in .env:
| Variable | Default | Description |
|---|---|---|
PGVECTOR_HOST |
localhost |
PostgreSQL host |
PGVECTOR_PORT |
5432 |
PostgreSQL port |
PGVECTOR_DATABASE |
vectordb |
Database name |
PGVECTOR_USER |
postgres |
Database user |
PGVECTOR_PASSWORD |
"" |
Database password |
No API keys, no model configuration. Embeddings run entirely locally.
Tools
| Tool | When to use |
|---|---|
index_pdfs_for_rag |
User wants PDFs searchable via natural language (knowledge base, RAG, Q&A). Starts background ingestion, returns task_id. |
check_indexing_progress |
After index_pdfs_for_rag, to monitor completion or when user asks "is it done yet?" |
cancel_pdf_indexing |
User wants to stop a running ingestion, or a task is stuck. |
Schema
CREATE TABLE documents (
id BIGSERIAL PRIMARY KEY,
collection_name TEXT NOT NULL,
file_hash TEXT NOT NULL,
file_path TEXT NOT NULL,
chunk_index INT NOT NULL,
content TEXT NOT NULL,
embedding vector(768),
metadata JSONB DEFAULT '{}'::jsonb,
created_at TIMESTAMPTZ DEFAULT NOW(),
UNIQUE(collection_name, file_hash, chunk_index)
);
CREATE INDEX idx_documents_collection ON documents (collection_name);
-- Auto-created after ingestion:
CREATE INDEX ON documents USING hnsw (embedding vector_cosine_ops)
WITH (m = 16, ef_construction = 200)
WHERE collection_name = ?;
Production Considerations
- Embedding model (~1.9GB) is downloaded on first run to
~/.cache/huggingface/hub/. Subsequent runs use the cached copy. - First load takes 10–30 seconds (model download + torch import). Lifespan handler pre-loads at startup.
- Memory: ~2GB RSS during ingestion (model + torch). Returns to ~200MB after ingestion completes.
- PostgreSQL: Ensure
max_connectionsis sufficient. The server uses a connection pool (min: 2, max: 8). - Retrieval: Add a
search_indexed_contenttool to query the indexed data — the schema and HNSW index are ready for it.
License
MIT
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。