KernelMind MCP
Enables AI agents to query Linux kernel source code, git history, LKML discussions, Patchwork patches, and documentation with evidence-ranked results, citations, and explicit assumptions or contradictions.
README
KernelMind MCP
Evidence-based Linux kernel engineering for AI agents — citations, not hallucinations.
KernelMind MCP is a Model Context Protocol server
that turns the public corpus of Linux kernel knowledge — git history, LKML /
lore.kernel.org, Patchwork, and Documentation/ — into a queryable, evidence-ranked
knowledge platform for AI coding and planning agents.
Every tool response carries an explicit evidence chain: which commit, which
mailing-list thread, which patch state transition supports the conclusion — plus
explicit assumptions and contradictions when the evidence is incomplete.
Performance claims are never fabricated; the system flags them
hardware_validation_required instead.
Why
LLMs hallucinate kernel facts — invented signatures, misremembered locking rules, APIs removed years ago cited as current. KernelMind's contract:
- Index primary sources, kept current by incremental sync (never full rebuild)
- Fuse dense vectors + BM25 + PostgreSQL full-text via Reciprocal Rank Fusion (k=60)
- Rank by a fixed evidence hierarchy: commit messages > LKML consensus > Documentation/ > maintainer comments > accepted patches > LWN > source code > rejected RFCs > vendor trees
- Return
evidence_sources,assumptions,contradictions, andhardware_validation_requiredon every engineering conclusion
Subsystem-agnostic by design: works identically on mainline, stable, linux-next, and vendor trees.
Features & Registered Tools
KernelMind MCP provides 16 specialized, evidence-first engineering tools across 5 categories:
| Category | Available MCP Tools | Description |
|---|---|---|
| Source Code | search_kernel_code, lookup_symbol |
Search kernel C source code and lookup symbol definitions with AST tree-sitter chunking |
| Git Intelligence | search_commits, get_commit_details, get_file_history, blame_line_range |
Inspect commit history, blame line ranges, and trace file evolution |
| Patchwork & LKML | search_patches, get_patch_details, search_lkml, get_thread_details |
Query patch discussions, LKML thread consensus, and patch state transitions |
| Research & Risk | analyze_patch_series, analyze_subsystem_risk |
Evaluate stability ratings, race/locking risk factors, and hardware validation requirements |
| Documentation & LWN | search_docs, get_doc_details, search_lwn, get_lwn_article |
Search kernel Documentation/ files and Linux Weekly News articles |
MCP prompts implement a 9-stage agent workflow: Knowledge Gathering → Subsystem Understanding → Architecture Modeling → Maintainer Review → Hypothesis Generation → Experiment Design → Implementation Planning → Patch Review → Self-Critique.
Architecture
AI Agent (Opencode / Claude Code / any MCP host)
│ JSON-RPC 2.0 — stdio (default) or Streamable HTTP
▼
MCP Gateway (validation, auth, audit)
▼
Tools → Hybrid Search (Qdrant + BM25 + PG FTS, RRF)
→ EvidenceCorrelator (priority tiers, assumptions, contradictions)
▼
PostgreSQL · Qdrant · Neo4j · Redis · MinIO
▲
Incremental Sync (Celery): git delta · LKML/lore · Patchwork
(state-transition tracking across all 12 patch states) · Documentation/
Indexing is kernel-aware: tree-sitter C grammar chunks at function/struct/macro
granularity without splitting function bodies; subsystem attribution is parsed
from MAINTAINERS (longest-prefix match) — no hardcoded maps.
Details: docs/ARCHITECTURE.md
Quick Start
git clone https://github.com/Reinazhard/kernelmind-mcp.git
cd kernelmind-mcp
cp .env.example .env # set EMBEDDING_* and any overrides
docker compose up -d --build
curl http://localhost:8080/health
Opencode (opencode.json)
{
"mcp": {
"kernelmind": {
"type": "local",
"command": ["docker", "compose", "exec", "-T", "kernelmind-mcp",
".venv/bin/python", "-m", "kernelmind.server", "--stdio"],
"enabled": true
}
}
}
Any stdio MCP client uses the same command. For remote hosts, set
KERNELMIND_TRANSPORT=streamable-http and connect to http://<host>:8080/mcp.
See docs/OPENCODE.md and docs/DEPLOYMENT.md.
Configuration
All config via environment variables (Pydantic, fail-fast at startup) —
see .env.example.
| Variable | Default | Purpose |
|---|---|---|
KERNELMIND_TRANSPORT |
stdio |
stdio or streamable-http |
KERNELMIND_EMBEDDING_BASE_URL / KERNELMIND_EMBEDDING_API_KEY / KERNELMIND_EMBEDDING_MODEL |
— | Embedding provider (required) |
KERNELMIND_POSTGRES_DSN, KERNELMIND_QDRANT_URL, KERNELMIND_NEO4J_URI, KERNELMIND_REDIS_URL, KERNELMIND_S3_ENDPOINT |
compose defaults | Storage backends |
KERNELMIND_HOST / KERNELMIND_PORT |
0.0.0.0 / 8080 |
HTTP Server Bind Address |
Project Status
Phase completion and known limitations: docs/PROGRESS.md. Available tool reference: docs/TOOLS.md. Deployment guide: docs/DEPLOYMENT.md.
License
GPL-2.0 — see 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 模型以安全和受控的方式获取实时的网络信息。