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).
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。