Solarium
A knowledge base MCP server backed by Qdrant vector database with local embeddings for semantic search and document management.
README
<p align="center"> <img src="logo.svg" width="128" height="128" alt="Solarium"> </p>
Solarium
A knowledge base MCP server backed by Qdrant vector database with local embeddings (nomic-embed-text-v1.5 via HuggingFace Transformers + ONNX Runtime).
Solarium runs as a local MCP server process — embeddings are computed on your machine, vectors are stored in a Qdrant instance of your choice (local or cloud).
Setup
Prerequisites
- Node.js 20+
- npm
Install dependencies
cd solarium
npm install
Build and link
npm run build
npm link
This builds the server and creates a global solarium command on your PATH.
Run the solarium binary
solarium
Pre-download the embedding model (optional but recommended)
The model (~130MB) is downloaded automatically on first use, but you can cache it ahead of time:
./bin/download-model.sh
Configure your Qdrant instance
Set your Qdrant API key in your shell profile (~/.zshrc or ~/.bashrc):
# Qdrant Cloud (Solarium)
export QDRANT_API_KEY=<your-qdrant-api-key>
Then reload your shell: source ~/.zshrc
Add to your Claude Code MCP config
Add the following to .mcp.json in any repo where you want Solarium available:
{
"mcpServers": {
"solarium": {
"command": "solarium",
"env": {
"QDRANT_URL": "https://your-cluster.cloud.qdrant.io:6333"
}
}
}
}
QDRANT_API_KEY is read from your shell environment automatically.
Verify
In Claude Code, run /mcp to confirm Solarium is connected, then try:
Search the knowledge base for "deployment architecture"
Available Tools
| Tool | Description |
|---|---|
store_document |
Store a document (chunks and embeds for semantic search) |
search |
Semantic search across all documents |
list_documents |
List all documents with metadata |
read_document |
Read full document content by ID |
update_document |
Update content or metadata (re-embeds if content changes) |
delete_document |
Delete a document and all its chunks |
list_tags |
List all tags with counts |
tag_document |
Add tags to a document |
untag_document |
Remove tags from a document |
Dashboard
Solarium includes a local web dashboard for browsing documents, semantic search, tag management, and analytics.
<p align="center"> <img src="screenshot.png" alt="Solarium Dashboard" width="800"> </p>
Build and run the dashboard
Reload your shell first.
npm run build:dashboard
solarium-dashboard
Then open http://localhost:3333 in your browser.
The dashboard requires the same QDRANT_URL and QDRANT_API_KEY environment variables as the MCP server. Set DASHBOARD_PORT to change the port (default: 3333).
Views
- Overview — collection stats (document/vector/point counts), recent documents, tag cloud
- Documents — paginated document list with tag filtering, full document detail with rendered markdown and chunk visualization, inline tag management (add/remove)
- Search — semantic search with relevance scores, snippets, and tag filtering
- Analytics — documents over time, tag distribution, chunk size distribution (Vega-Lite charts), collection stats
Architecture
The dashboard runs as a separate process from the MCP server (which uses stdio). Both share the same source code — Qdrant client, tools, config, and embedding pipeline.
- Server-driven rendering — HTML is rendered on the server from ClojureScript hiccup, streamed to the browser
- SSE + Idiomorph — live updates via Server-Sent Events with DOM morphing (polls Qdrant every 60s)
- Tailwind CSS +
@tailwindcss/typography— styling with theproseclass for markdown content - Vega-Lite — interactive charts, lazy-loaded from CDN only on the analytics page
- No frontend framework — no React, no client-side state management; ~30 lines of client JS for SSE wiring
Configuration
All configuration is via environment variables:
| Variable | Default | Description |
|---|---|---|
QDRANT_URL |
http://localhost:6333 |
Qdrant server URL |
QDRANT_API_KEY |
(none) | Qdrant API key (required for cloud) |
COLLECTION_NAME |
knowledge |
Qdrant collection name |
MODEL_NAME |
nomic-ai/nomic-embed-text-v1.5 |
HuggingFace embedding model |
CHUNK_MAX_CHARS |
1600 |
Max characters per chunk |
CHUNK_OVERLAP |
200 |
Overlap between chunks |
DASHBOARD_PORT |
3333 |
Dashboard HTTP server port |
Development
# Watch mode — MCP server
npm run watch
# Watch mode — dashboard
npm run watch:dashboard
# Watch both
npm run watch:all
# Run tests
npm test
Built with shadow-cljs (ClojureScript).
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.