mcp-rag-assistant
MCP server that provides 8 local RAG tools using LlamaIndex and Ollama, enabling AI-powered document querying, summarization, analysis, and comparison over PDFs, DOCX, XLSX, and CSV files.
README
MCP-Powered AI Assistant (Local — LlamaIndex + Ollama)
Privacy-first document intelligence: all models run locally via Ollama — no data leaves your machine.
What is MCP?
Model Context Protocol (MCP) is an open standard (by Anthropic) that defines how AI models discover and invoke tools at runtime. Think of it as a "USB-C port for AI" — any MCP-compatible client (Claude Desktop, your own agent, etc.) can connect to any MCP server and immediately use its tools.
MCP vs. Advanced RAG — What's the Difference?
| Dimension | Advanced RAG | MCP |
|---|---|---|
| Purpose | Improve retrieval accuracy | Standardise tool/capability exposure |
| Core idea | Better chunking, re-ranking, hybrid search | JSON-RPC tool registry with discovery |
| What the LLM gets | Retrieved context injected into prompt | A menu of callable functions with schemas |
| Execution | Single pipeline (query → retrieve → generate) | Multi-step agent loop (plan → pick tool → call → observe → repeat) |
| Tools | Retrieval only | Any function: retrieval, APIs, databases, code |
| State | Stateless per query | Stateful agent sessions possible |
| This project | RAG is one tool inside the MCP server | MCP wraps 8 RAG tools, discoverable at runtime |
In short: Advanced RAG makes retrieval smarter. MCP makes the entire AI system composable and interoperable.
Project Architecture
mcp_rag_assistant/
├── config.py ← Central config (LLM, embed, chunking, server)
├── rag_engine.py ← LlamaIndex: load docs → build index → query engine
├── main.py ← CLI entrypoint (serve / index / query / demo)
├── mcp_client.py ← Example client that calls server tools
│
├── mcp_server/
│ └── server.py ← HTTP JSON-RPC server exposing all tools
│
├── tools/
│ └── rag_tools.py ← 8 MCP tool implementations
│
├── utils/
│ └── logger.py ← Structured logging
│
├── my_data/ ← ⬅ DROP YOUR FILES HERE (PDF, DOCX, XLSX, CSV)
├── storage/ ← ChromaDB persistence (auto-created)
├── logs/ ← Log files (auto-created)
│
├── requirements.txt
├── .env.example
├── .gitignore
└── README.md
Data Flow
User Query
│
▼
MCP Client (mcp_client.py or Claude Desktop or your agent)
│ JSON-RPC POST /mcp {"method": "tools/call", "params": {...}}
▼
MCP Server (mcp_server/server.py)
│ dispatches to matching tool function
▼
Tool Function (tools/rag_tools.py)
│ calls get_query_engine().query(...)
▼
LlamaIndex Query Engine (rag_engine.py)
│ embeds query with qwen3-embedding:0.6b via Ollama
▼
ChromaDB Vector Store
│ returns top-K similar chunks
▼
Ollama LLM (llama3 or mistral)
│ synthesises answer from retrieved context
▼
JSON response back through MCP → Client
Available MCP Tools
| Tool | Description |
|---|---|
query_documents |
General Q&A over all indexed documents |
list_indexed_files |
Show files in my_data/ |
rebuild_index |
Re-index after adding/removing files |
summarize_document |
Summarise a specific file by name |
analyze_data |
Plain-English data analysis (CSV/XLSX) |
generate_report |
Generate summary / detailed / executive report |
compare_documents |
Compare two documents on a given aspect |
extract_entities |
Extract people, orgs, dates, numbers |
Prerequisites
- Python 3.10+
- Ollama running locally — ollama.com
- Models already pulled (you have these):
llama3:latestmistral:latestqwen3-embedding:0.6b
Setup
# 1. Clone / unzip the project
cd mcp_rag_assistant
# 2. Create virtual environment
python -m venv venv
source venv/bin/activate # Windows: venv\Scripts\activate
# 3. Install dependencies
pip install -r requirements.txt
# 4. Configure (optional — defaults work out of the box)
cp .env.example .env
# Edit .env to change models, ports, chunk sizes etc.
# 5. Add your documents
# Copy PDFs, DOCX, XLSX, CSV files into:
# my_data/
# 6. Build the index
python main.py index
# 7. Start the MCP server
python main.py serve
Usage
Start the server
python main.py serve
# MCP server listening on http://0.0.0.0:8080
One-shot query (no server needed)
python main.py query "What are the key findings in the Q1 report?"
Run the demo client (server must be running)
# In a second terminal:
python main.py demo
Rebuild index after adding new files
python main.py index
# or via MCP tool:
# call rebuild_index tool from any client
Health check
GET http://localhost:8080/health
GET http://localhost:8080/tools
Switching Models
Edit config.py or your .env:
# Use mistral instead of llama3
LLM_MODEL=mistral:latest
# Use nomic-embed-text for embeddings
EMBED_MODEL=nomic-embed-text:latest
Tuning Chunk Size
In config.py or .env:
| Setting | Default | Notes |
|---|---|---|
CHUNK_SIZE |
256 | Tokens per chunk. Smaller = more precise retrieval |
CHUNK_OVERLAP |
25 | Overlap between chunks. Helps preserve context at boundaries |
SIMILARITY_TOP_K |
5 | Chunks retrieved per query |
RESPONSE_MODE |
compact | compact | tree_summarize | refine |
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。