Knowledge Base MCP Server
Provides semantic search over a self-building personal technical knowledge base that automatically collects and distills content from GitHub Trending, AI news, and arXiv.
README
Knowledge Base — Self-Building MCP Server
A personal technical knowledge base that builds itself: a GitHub Actions pipeline collects from GitHub Trending, AI news RSS (incl. Anthropic via HTML scraping), and arXiv daily, distills the content into structured wiki pages with an LLM, and an MCP server (deployable via Docker / Portainer) serves semantic search over it.
Inspired by mufans/knowledge-base and the Karpathy LLM Wiki method.
How it works
A1 host (single container: knowledge-mcp) — fully local, no GitHub in daily loop
├─ collect thread (UTC 16:00): scripts/collect.py → /data/kb-self/raw/inbox/
├─ distill thread (UTC 16:45): scripts/distill.py → /data/kb-self/wiki/
│ (LLM key lives ONLY in the container env, never touches GitHub)
└─ serves /mcp (Streamable HTTP, optional Bearer auth) over the local wiki
Security note: collection and distillation both run entirely on your A1 machine. GitHub only hosts the source code and builds the Docker image — it never sees collected data or the LLM API key.
Repository layout
.github/workflows/
build.yml # build arm64 image → ghcr.io/zhengr/knowledge-mcp
knowledge.yml # daily collect only (distill runs locally on A1)
Dockerfile
docker-compose.yml
scripts/
collect.py # free collectors (GitHub + arXiv)
distill.py # LLM → wiki pages (OpenAI-compatible API)
update_wiki.py # standalone updater (used inside the container)
server.py # MCP server (search_kb / get_entity / list_recent)
pyproject.toml
raw/inbox/ # collected raw content (auto-generated)
wiki/ # distilled knowledge (auto-generated)
Environment variables
| Variable | Default | Description |
|---|---|---|
KNOWLEDGE_BASE_PATH |
/kb |
Knowledge base root (contains wiki/) |
KB_TRANSPORT |
http |
http / sse / stdio |
KB_HOST |
0.0.0.0 |
Bind address |
KB_PORT |
8000 |
Listen port |
MCP_AUTH_TOKEN |
(empty) | If set, requires Authorization: Bearer <token> |
KB_UPDATE_URL |
repo tarball | Override the auto-update source URL |
Deploy (single container)
docker run -d --name knowledge-mcp -p 8000:8000 \
-e KNOWLEDGE_BASE_PATH=/data/kb-self \
-e MCP_AUTH_TOKEN=your-secret-token \
-v /opt:/data:rw \
ghcr.io/zhengr/knowledge-mcp:latest
The container both serves the MCP endpoint and auto-updates the wiki
in-place (writes to the mounted /data/kb-self).
Connect a client (Claude Code / Cursor)
{
"mcpServers": {
"knowledge": {
"url": "http://<host>:8000/mcp",
"headers": { "Authorization": "Bearer your-secret-token" }
}
}
}
Configure the LLM (for distillation)
Set these as repository secrets (Settings → Secrets → Actions):
| Secret | Example |
|---|---|
LLM_API_BASE |
https://api.openai.com/v1 |
LLM_API_KEY |
sk-... |
LLM_MODEL |
gpt-4o-mini |
Tools
search_kb(query, category?, limit?)— full-text search over the wikiget_entity(name)— fetch one wiki pagelist_recent(limit?, days?, min_score?)— recently updated pages
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。