case-chat
A conversational chat interface that uses RAG over a synthetic test corpus and a domain-knowledge corpus, exposing retrieval via MCP.
README
case-chat
A proof-of-concept conversational chat interface backed by DiffusionGemma served
via vLLM (OpenAI-compatible /v1) on a cloud-rented RTX 5090. It answers
questions using RAG over two read-only knowledge sources:
- the synthetic test corpus of raw source documents (fictional Holcomb family Arkansas guardianship case), and
- the existing domain-knowledge corpus (legal / behavioral / scripture), re-embedded into Qdrant and reachable via MCP.
It also exposes a structured fake-case dataset built from the synthetic corpus ground-truth (timeline / entities / facts / flags / observations) so exact questions like "when was the guardianship petition filed?" resolve against structured data — a stand-in for what case-project's extraction pipeline will eventually provide.
Hard boundaries
- No Athena. LLM + embeddings go through vLLM / a Qwen3-Embedding-4B
/embeddingsendpoint, never the Athena daemon. - No extracted data. RAG reads only raw source documents + the
domain-knowledge corpus. case-project's
casedb(timeline events, evidence, observations, resolved participants, …) is off-limits. The fake-case dataset here is synthesized from the synthetic corpus's ground-truth, which is fictional — not the realcasedb. - Data sovereignty. Only the fictional synthetic corpus and the
non-sensitive domain-knowledge reference text leave local hardware. Real
case-data/never does.
Architecture
[Web app + chat orchestrator] ──MCP stdio──▶ [MCP retrieval server] ──▶ Qdrant
│ │
│ OpenAI /v1 (tools) ├─ /embeddings ─▶ Qwen3-Embedding-4B
▼ │ (TEI on box / local fallback)
DiffusionGemma (vLLM, 4-bit) └─ SQLite (fake-case dataset)
Embedding contract (load-bearing)
Qwen/Qwen3-Embedding-4B · 2560-dim · cosine · L2-normalized · asymmetric
(queries wrapped Instruct: …\nQuery: …, documents bare). Kept identical to
domain-knowledge's build side so vectors converge. See
case_chat/embeddings/client.py.
Decisions
Architecture decisions are recorded under docs/decisions/.
Status
POC under construction. See the implementation plan / todo list.
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
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
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.