reg-docs-mcp
An MCP server that answers questions over insurance and regulatory documents using retrieval-augmented generation, returning grounded, cited passages via local embeddings and OpenSearch.
README
reg-docs-mcp
An MCP (Model Context Protocol) server that answers questions over insurance and regulatory documents using retrieval-augmented generation (RAG). Any MCP-compatible AI client (Claude Desktop, Claude Code, Cursor) can call it as a tool to get grounded, cited answers instead of relying on the model's memory.
Everything in this stack is free and runs locally — no AWS account, no API keys, no per-call cost.
| Component | Technology |
|---|---|
| Embeddings | sentence-transformers (all-MiniLM-L6-v2), running locally on CPU |
| Vector store | Open-source OpenSearch, self-hosted via Docker |
| Tool protocol | Official Python MCP SDK (mcp) |
How it works
- Regulatory documents (plain text) are chunked into overlapping passages.
- Each chunk is embedded locally with a small sentence-transformer model.
- Chunks and their embeddings are indexed into OpenSearch as
knn_vectorfields. - The MCP server exposes a
search_docstool: given a natural-language query, it embeds the query the same way, runs a k-NN similarity search, and returns the top matching passages with their source file and score. - An AI client calling the tool gets real, citable text back — not a hallucinated summary.
Prerequisites
- Python 3.10+
- Docker (for local OpenSearch)
Setup
python3 -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -r requirements.txt
cp .env.example .env
docker compose up -d # starts OpenSearch + OpenSearch Dashboards
python3 ingest.py # chunks, embeds, and indexes the sample docs
python3 mcp_server.py # runs the MCP server on stdio
The first ingest.py run downloads the embedding model from Hugging Face
(~90 MB) and caches it locally — after that, everything runs offline.
Using it from an AI client
Add this to your MCP client config (e.g. Claude Desktop's
claude_desktop_config.json), using absolute paths:
{
"mcpServers": {
"reg-docs": {
"command": "/absolute/path/to/reg-docs-mcp/.venv/bin/python",
"args": ["/absolute/path/to/reg-docs-mcp/mcp_server.py"]
}
}
}
Then ask the client something like "What's the difference between the SCR
and the MCR under Solvency II?" and it will call search_docs and answer
from the retrieved passages.
Inspecting the index
OpenSearch Dashboards is available at http://localhost:5601 once the containers are up. Under Dev Tools, you can query the index directly to confirm ingestion worked:
GET reg-docs/_search
{
"query": { "match_all": {} },
"size": 3
}
Adding real documents
data/sample_docs/ ships with a few short, original placeholder summaries
(written for this project, not copied from any official source) so the
pipeline works out of the box. For a fuller, more realistic demo, add
plain-text extracts from public regulatory sources, for example:
- FCA Handbook — https://www.handbook.fca.org.uk
- Bank of England / PRA Rulebook — https://www.prarulebook.co.uk
- EIOPA (Solvency II) — https://www.eiopa.europa.eu
- IFRS Foundation — https://www.ifrs.org
Drop .txt files into data/sample_docs/ and re-run python3 ingest.py.
Project structure
reg-docs-mcp/
├── requirements.txt
├── docker-compose.yml OpenSearch + OpenSearch Dashboards, local only
├── .env.example
├── config.py environment/config loading
├── chunk.py paragraph/sentence-aware text chunking
├── embeddings.py local embedding model wrapper
├── opensearch_client.py index creation, bulk indexing, k-NN search
├── ingest.py ingestion pipeline entry point
├── mcp_server.py MCP server exposing the search_docs tool
└── data/
└── sample_docs/ sample text documents
All modules sit flat in the project root rather than inside a package —
MCP clients launch mcp_server.py directly as a script, and package-
relative imports don't resolve in that context.
Notes
- The OpenSearch containers disable the security plugin for local development convenience. Do not use this configuration for anything exposed beyond localhost.
all-MiniLM-L6-v2produces 384-dimensional embeddings; if you swap in a different embedding model, updateEMBEDDING_DIMSinconfig.pyto match.
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.