knowledgeplane
MCP server that gives AI agents and teams persistent, shared memory using a knowledge graph with vector embeddings, automatic consolidation of related facts, and hybrid search.
README
<p align="center"> <img src="docs/images/logo.png" width="120" alt="Knowledge Plane" /> </p>
<h1 align="center">Knowledge Plane</h1>
<p align="center"> Shared memory for AI agents and teams -- stops your tools from forgetting. </p>
<p align="center"> <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-blue.svg" alt="License" /></a> <img src="https://img.shields.io/badge/node-%3E%3D20-brightgreen.svg" alt="Node" /> <img src="https://img.shields.io/badge/docker-required-blue.svg" alt="Docker" /> </p>
<p align="center"> <img src="docs/images/dashboard.png" alt="Knowledge Plane Dashboard" width="800" /> </p>
What is Knowledge Plane?
Knowledge Plane is an MCP server that gives AI agents and teams persistent, shared memory. It stores facts as a knowledge graph with vector embeddings, automatically consolidates related facts into knowledge cards, and provides hybrid search (vector + graph traversal). Native MCP protocol support means any MCP-compatible AI tool (Claude, Cursor, etc.) can read and write shared knowledge.
Why Knowledge Plane?
Memory layers for AI exist (Mem0, Zep, Letta), but they're built around flat vector stores -- good for retrieval, less good for understanding how things relate. Knowledge Plane stores facts as a graph with typed relations, so "Alice manages Bob" is a first-class edge you can traverse, not a blob of text you hope cosine similarity resurfaces. Background workers continuously consolidate related facts into knowledge cards, building institutional knowledge instead of just accumulating embeddings. And it's designed for teams from the start: multi-workspace, multi-agent, multi-tool -- shared memory across your entire AI stack, not just one chatbot.
How It Works
Your team runs AI agents across different tools -- a dev agent in the IDE, a PM agent in the browser, a support agent in Slack. On Monday, the dev agent learns that the payments API was refactored. On Wednesday, the PM agent is planning a sprint and needs that context. Without shared memory, it doesn't have it. With Knowledge Plane, the dev agent wrote that fact once, the consolidation worker linked it to the payments service card, and now any agent in any tool can find it through search or graph traversal.
Open Infrastructure
Built on MCP (Model Context Protocol), the emerging open standard for AI tool integration. Fully self-hostable -- your knowledge stays on your infrastructure. Apache-2.0 licensed, no telemetry, no vendor lock-in. Your data, your rules.
Built by Camplight, a cooperative of AI-native teams across Europe. Used internally to power knowledge sharing across Juma.ai and Slack-integrated marketing agents.
Features
- Persistent agent memory -- Facts stored in ArangoDB knowledge graph with vector embeddings
- MCP-native -- Drop-in memory for Claude Desktop, Cursor, and any MCP client
- Hybrid search -- Vector similarity + graph traversal + optional BM25
- Auto-consolidation -- Background workers merge related facts into knowledge cards
- File upload and extraction -- Upload documents, extract facts automatically
- Web dashboard -- Browse, search, and manage your knowledge graph
- Multi-workspace -- Isolated knowledge spaces per team or project
- OAuth + API keys -- Google/GitHub OAuth and API key authentication
- REST API -- Full CRUD API alongside the MCP server
- Audit trails -- Track who created and modified every fact
Quick Start
# Clone and install
git clone https://github.com/camplight/knowledgeplane.git
cd knowledgeplane
npm run bootstrap
# Set up environment
./scripts/setup-env.sh # Creates .env files from examples
# Start everything (ArangoDB + all services)
npm run dev
Services start at:
| Service | URL |
|---|---|
| Web Dashboard | http://localhost:3000 |
| MCP Server | http://localhost:8080 |
| REST API | http://localhost:8081 |
| ArangoDB | http://localhost:8529 |
For detailed setup including OAuth and ngrok, see Getting Started.
MCP Integration
Claude Desktop
Add to your Claude Desktop MCP config:
Option 1: HTTP/SSE (recommended)
{
"mcpServers": {
"knowledgeplane": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Option 2: stdio adapter
{
"mcpServers": {
"knowledgeplane": {
"command": "node",
"args": ["apps/mcp-server/dist/mcp/adapter.js"],
"env": {
"KNOWLEDGEPLANE_API_URL": "http://localhost:8080",
"KNOWLEDGEPLANE_API_KEY": "YOUR_API_KEY"
}
}
}
}
Architecture
knowledgeplane/
├── apps/
│ ├── mcp-server/ # MCP protocol server (Fastify)
│ ├── rest-api/ # REST API (Express)
│ ├── webapp/ # Web dashboard (Next.js)
│ └── background-workers/ # Consolidation & embeddings
├── packages/
│ ├── db/ # ArangoDB models & queries
│ ├── aimodel/ # LLM abstraction layer
│ ├── api-core/ # Shared API utilities
│ └── file-processor/ # Document parsing & extraction
└── infra/ # Docker Compose configs
Documentation
| Guide | Description |
|---|---|
| Getting Started | Quick start and setup |
| Development Guide | Local development with ngrok |
| Deployment Guide | Cloud deployment (Railway, etc.) |
| Environment Setup | All environment variables |
| API Specification | Complete API reference |
Knowledge Plane Cloud
This repo is the self-hosted, DIY version. If you'd rather not manage the infrastructure yourself, Knowledge Plane Cloud offers a managed deployment with everything pre-configured. And if you need a full agentic memory overhaul -- integrating shared knowledge across your team's AI tools and workflows -- Camplight (the team behind Knowledge Plane) does that as a service.
Contributing
We're actively looking for help with:
- MCP tool coverage -- adding new tools and improving existing ones
- Dashboard UI -- the web interface needs polish and new views
- Documentation -- guides, tutorials, and API docs
- Testing -- integration tests, edge cases, benchmark coverage
See CONTRIBUTING.md for setup instructions and guidelines.
License
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。