Sekha MCP Server
This MCP server exposes Sekha memory tools (store, search, update, etc.) to any MCP-compatible client, enabling persistent conversation memory across Claude Desktop, Claude Code, and other applications.
README
Sekha MCP Server
Model Context Protocol Server for Sekha Memory
🆕 v0.2.0 Release - Multi-Provider Support
Sekha MCP v0.2.0 is now compatible with the new Sekha v0.2.0 multi-provider architecture!
What's New:
- ✅ Works with Sekha v0.2.0 controller's multi-provider routing
- ✅ Automatic provider fallback (Ollama, OpenAI, Anthropic, etc.)
- ✅ Vision support (GPT-4o, Kimi 2.5) - just include images!
- ✅ Cost-aware model selection
- ✅ Multi-dimensional embeddings (per-dimension ChromaDB collections)
- ✅ Claude Desktop & Claude Code support - memory in both apps!
- ✅ No API changes - fully backward compatible!
What is Sekha MCP?
MCP (Model Context Protocol) server that exposes Sekha memory tools to any MCP-compatible client:
- ✅ Claude Desktop - Anthropic's desktop app
- ✅ Claude Code - VS Code extension (works with Ollama, Anthropic, or any provider)
- ✅ Any MCP client - Standard protocol implementation
Supported Tools:
- ✅
memory_store- Save conversations - ✅
memory_search- Semantic search - ✅
memory_get_context- Retrieve relevant context - ✅
memory_update- Update conversation metadata - ✅
memory_prune- Get cleanup recommendations - ✅
memory_export- Export your data - ✅
memory_stats- View usage statistics
Total: 7 MCP tools
📚 Documentation
Complete guide: docs.sekha.dev/integrations/mcp
🚀 Quick Start
1. Install Sekha
# Deploy Sekha v0.2.0 stack with multi-provider support
git clone https://github.com/sekha-ai/sekha-docker.git
cd sekha-docker
docker compose -f docker/docker-compose.prod.yml up -d
2. Configure Your MCP Client
Option A: Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
{
"mcpServers": {
"sekha": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--network=host",
"ghcr.io/sekha-ai/sekha-mcp:v0.2.0"
],
"env": {
"CONTROLLER_URL": "http://localhost:8080",
"CONTROLLER_API_KEY": "your-mcp-api-key-here"
}
}
}
}
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json
Option B: Claude Code (VS Code Extension)
Add to VS Code settings.json or workspace config:
{
"mcpServers": {
"sekha": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--network=host",
"ghcr.io/sekha-ai/sekha-mcp:v0.2.0"
],
"env": {
"CONTROLLER_URL": "http://localhost:8080",
"CONTROLLER_API_KEY": "your-mcp-api-key-here"
}
}
}
}
Claude Code Configuration:
Claude Code lets you choose your LLM provider separately from memory:
{
// Sekha provides memory (via MCP)
"mcpServers": {
"sekha": { /* config above */ }
},
// Configure your LLM provider (Claude Code supports multiple)
"claudeCode.apiProvider": "ollama", // or "anthropic"
"claudeCode.ollamaUrl": "http://localhost:11434",
"claudeCode.ollamaModel": "llama3.1:8b"
}
This means:
- Use Ollama (or other LLM) locally for generation (fast, private, free)
- Use Sekha MCP for memory (persistent across sessions)
- Best of both worlds!
3. Restart Your Client
- Claude Desktop: Restart the app
- Claude Code: Reload VS Code window (
Cmd+Shift+P→ "Reload Window")
Sekha memory tools will now appear!
See setup guides:
🎯 Use Cases
Claude Desktop - Interactive Conversations
- Full-featured desktop app with Sekha memory
- Perfect for brainstorming, research, general chat
- Uses Anthropic's Claude models
Claude Code - Development Workflow Examples
- VS Code extension with code-aware features
- Use with Ollama for fast, local, private coding
- Or use with Anthropic/OpenAI for powerful cloud models
- Sekha memory works with any provider you configure
API Integration - Programmatic Access
- Use sekha-proxy for OpenAI-compatible API
- Multi-provider routing via LLM bridge
- Same memory as Claude apps
🔧 Development
# Clone
git clone https://github.com/sekha-ai/sekha-mcp.git
cd sekha-mcp
# Install
pip install -e .
# Run locally
python -m sekha_mcp
# Test
pytest
📚 MCP Tools Reference
memory_store
Store a conversation in Sekha.
Parameters:
label(string) - Conversation labelmessages(array) - Message array (supports images in v0.2.0!)folder(string, optional) - Organization folderimportance(int, optional) - 1-10 scale
memory_search
Search conversations semantically.
Parameters:
query(string) - Search querylimit(int) - Max resultsfolder(string, optional) - Search within folder
memory_get_context
Assemble optimal context for LLM.
Parameters:
query(string) - Context querycontext_budget(int) - Token limitfolders(array, optional) - Limit to specific folders
memory_update
Update conversation metadata.
Parameters:
conversation_id(string) - Conversation UUIDlabel(string, optional) - New labelfolder(string, optional) - New folderimportance(int, optional) - New importance (1-10)status(string, optional) - active/archived
memory_prune
Get cleanup recommendations.
Parameters:
min_age_days(int, optional) - Minimum agemax_importance(int, optional) - Max importance to considerlimit(int, optional) - Max suggestions
memory_export
Export conversations.
Parameters:
format(string) - json or markdownfolder(string, optional) - Export specific folder
memory_stats
Get memory usage statistics.
Parameters: None
Returns:
- Total conversations
- Total messages
- Storage usage
- Folder breakdown
- Provider stats (v0.2.0) - which models are being used
🏗️ Architecture
┌─────────────────────────────────────────────┐
│ MCP Clients │
│ - Claude Desktop (Anthropic) │
│ - Claude Code (Ollama/Anthropic/etc.) │
│ - Any MCP-compatible client │
└────────────────┬────────────────────────────┘
│
▼
┌────────────────┐
│ Sekha MCP │ ← This repository
│ Server │
└────────┬───────┘
│
▼
┌────────────────┐
│ Controller │ ← Memory APIs
│ (Rust) │
└────────┬───────┘
│
▼
┌────────────────┐
│ ChromaDB │ ← Vector storage
│ Redis │ ← Cache
└────────────────┘
Separate from LLM routing:
┌─────────────────────────────────────────────┐
│ API Clients → Proxy → Bridge → Providers │
│ (OpenAI SDK compatible) │
└─────────────────────────────────────────────┘
Key Points:
- MCP provides memory tools only
- Claude Desktop/Code handle their own LLM connections
- Controller stores all conversations regardless of source
- Same memory accessible from Claude apps and API
🔗 Links
- Main Repo: sekha-controller
- Proxy (API): sekha-proxy
- Docker Deploy: sekha-docker
- Docs: docs.sekha.dev
- Website: sekha.dev
- Discord: discord.gg/sekha
📝 Changelog
See CHANGELOG.md for full release history.
📝 License
AGPL-3.0 - License Details
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。