Zettelkasten MCP

MCP文档知识

提供方 Liam-Deacon

文档知识 未标注 无需鉴权 社区 / 第三方
查看接入方式

Implements the Zettelkasten knowledge management methodology, allowing you to create, link, explore and synthesize atomic notes through Claude and other MCP-compatible clients.

一句话选型结论

按资料字段整理

Zettelkasten MCP 属于文档知识类 MCP 服务器,传输方式未标注,无需鉴权,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式未标注 鉴权无需鉴权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

未标注 无需鉴权
上游未给出传输方式
pip install pre-commit

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zettelkasten MCP当前 未标注 未标注 未标注 有 2026-05-17
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Liam-Deacon上游标注的维护方 Liam-Deacon
分类文档知识本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Python本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

16.2 KB
来自项目仓库与上游目录的原文,未做删改

Zettelkasten MCP Server

A Model Context Protocol (MCP) server that implements the Zettelkasten knowledge management methodology, allowing you to create, link, explore and synthesize atomic notes through Claude and other MCP-compatible clients.

What is Zettelkasten?

The Zettelkasten method is a knowledge management system developed by German sociologist Niklas Luhmann, who used it to produce over 70 books and hundreds of articles. It consists of three core principles:

  1. Atomicity: Each note contains exactly one idea, making it a discrete unit of knowledge
  2. Connectivity: Notes are linked together to create a network of knowledge, with meaningful relationships between ideas
  3. Emergence: As the network grows, new patterns and insights emerge that weren't obvious when the individual notes were created

What makes the Zettelkasten approach powerful is how it enables exploration in multiple ways:

  • Vertical exploration: dive deeper into specific topics by following connections within a subject area.
  • Horizontal exploration: discover unexpected relationships between different fields by traversing links that cross domains.

This structure invites serendipitous discoveries as you follow trails of thought from note to note, all while keeping each piece of information easily accessible through its unique identifier. Luhmann called his system his "second brain" or "communication partner" - this digital implementation aims to provide similar benefits through modern technology.

Features

  • Create atomic notes with unique timestamp-based IDs
  • Link notes bidirectionally to build a knowledge graph
  • Tag notes for categorical organization
  • Search notes by content, tags, or links
  • Use markdown format for human readability and editing
  • Integrate with Claude through MCP for AI-assisted knowledge management
  • Dual storage architecture (see below)
  • Synchronous operation model for simplified architecture

Examples

  • Knowledge creation: A small Zettelkasten knowledge network about the Zettelkasten method itself

Note Types

The Zettelkasten MCP server supports different types of notes:

Type Handle Description
Fleeting notes fleeting Quick, temporary notes for capturing ideas
Literature notes literature Notes from reading material
Permanent notes permanent Well-formulated, evergreen notes
Structure notes structure Index or outline notes that organize other notes
Hub notes hub Entry points to the Zettelkasten on key topics

Link Types

The Zettelkasten MCP server uses a comprehensive semantic linking system that creates meaningful connections between notes. Each link type represents a specific relationship, allowing for a rich, multi-dimensional knowledge graph.

Primary Link Type Inverse Link Type Relationship Description
reference reference Simple reference to related information (symmetric relationship)
extends extended_by One note builds upon or develops concepts from another
refines refined_by One note clarifies or improves upon another
contradicts contradicted_by One note presents opposing views to another
questions questioned_by One note poses questions about another
supports supported_by One note provides evidence for another
related related Generic relationship (symmetric relationship)

Prompting

To ensure maximum effectiveness, we recommend using a system prompt ("project instructions"), project knowledge, and an appropriate chat prompt when asking the LLM to process information, or explore or synthesize your Zettelkasten notes. The docs directory in this repository contains the necessary files to get you started:

System prompts

Pick one:

  • system-prompt.md
  • system-prompt-with-protocol.md

Project knowledge

For end users:

  • zettelkasten-methodology-technical.md
  • link-types-in-zettelkasten-mcp-server.md
  • (more info relevant to your project)

Chat Prompts

  • chat-prompt-knowledge-creation.md
  • chat-prompt-knowledge-creation-batch.md
  • chat-prompt-knowledge-exploration.md
  • chat-prompt-knowledge-synthesis.md

Project knowledge (dev)

For developers and contributors:

  • Example - A simple MCP server.md
  • MCP Python SDK-README.md
  • llms-full.txt

NB: Optionally include the source code with a tool like repomix.

Storage Architecture

This system uses a dual storage approach:

  1. Markdown Files: All notes are stored as human-readable Markdown files with YAML frontmatter for metadata. These files are the source of truth and can be:
  • Edited directly in any text editor
  • Placed under version control (Git, etc.)
  • Backed up using standard file backup procedures
  • Shared or transferred like any other text files
  1. Database Index: Functions as an indexing layer that:
    - Facilitates efficient querying and search operations
    - Enables Claude to quickly traverse the knowledge graph
    - Maintains relationship information for faster link traversal
    - Is automatically rebuilt from Markdown files when needed
    - Uses SQLite by default; provide a SQLAlchemy URL via ZETTELKASTEN_DATABASE for PostgreSQL or other backends

If you edit Markdown files directly outside the system, you'll need to run the zk_rebuild_index tool to update the database. The database itself can be deleted at any time - it will be regenerated from your Markdown files.

Installation

Installing via Smithery

To install Zettelkasten MCP Server for Claude Desktop automatically via Smithery:```bash
npx -y @smithery/cli install zettelkasten-mcp --client claude


### Via uvx```bash
uvx --from=git+https://github.com/entanglr/zettelkasten-mcp zettelkasten-mcp --notes-dir ./data/notes --database ./data/db/zettelkasten.db

Via pipx (native macOS/Linux/Windows)

Install from GitHub:```bash
pipx install "git+https://github.com/entanglr/zettelkasten-mcp.git"


If/when published on PyPI, install from PyPI instead:```bash
pipx install zettelkasten-mcp

Run the server:```bash
zettelkasten-mcp --notes-dir ./data/notes --database ./data/db/zettelkasten.db


### Native Apple Silicon (non-Docker)

On Apple Silicon Macs, prefer `pipx`/`uvx` for native `darwin/arm64`
execution. Docker images are Linux-only (`linux/amd64`, `linux/arm64`) and do
not provide a native `darwin` container target.

### Docker image architecture support

The `latest` image tag is published as a multi-arch image manifest with:

- `linux/amd64`
- `linux/arm64`

Backend support in the container image differs by architecture:

| Backend       | `linux/amd64` | `linux/arm64` |
| ------------- | ------------- | ------------- |
| SQLite        | Supported     | Supported     |
| PostgreSQL    | Supported     | Supported     |
| MySQL/MariaDB | Supported     | Supported     |
| SQL Server    | Supported     | Not supported |

`linux/arm64` images intentionally skip SQL Server ODBC driver installation
(`msodbcsql18`) because upstream driver packaging is currently amd64-focused in
this Docker build strategy.

### Local Development```bash
# Clone the repository
git clone https://github.com/entanglr/zettelkasten-mcp.git
cd zettelkasten-mcp

# Create a virtual environment with uv
uv venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate

# Install dependencies
uv add "mcp[cli]"

# Install dev dependencies
uv sync --all-extras

Configuration

Create a .env file in the project root by copying the example:```bash
cp .env.example .env


Then edit the file to configure your connection parameters.

To use PostgreSQL instead of the bundled SQLite database, install the optional driver and point `ZETTELKASTEN_DATABASE` at a SQLAlchemy URL:```bash
pip install "zettelkasten-mcp[postgresql]"
export ZETTELKASTEN_DATABASE="postgresql+psycopg://user:password@localhost:5432/zettelkasten"

Using pipx:```bash
pipx install "zettelkasten-mcp[postgresql]"
export ZETTELKASTEN_DATABASE="postgresql+psycopg://user:password@localhost:5432/zettelkasten"


`ZETTELKASTEN_DATABASE` accepts either a filesystem path (default `./data/db/zettelkasten.db`) or any SQLAlchemy-compatible URL. Legacy `ZETTELKASTEN_DATABASE_PATH` / `ZETTELKASTEN_DATABASE_URL` variables are still honored for backward compatibility.

For MySQL or MariaDB support, install the `mysql` extra and supply a URL using the `pymysql` driver:```bash
pip install "zettelkasten-mcp[mysql]"
export ZETTELKASTEN_DATABASE="mysql+pymysql://user:password@localhost:3306/zettelkasten"

Using pipx:```bash
pipx install "zettelkasten-mcp[mysql]"
export ZETTELKASTEN_DATABASE="mysql+pymysql://user:password@localhost:3306/zettelkasten"


For Microsoft SQL Server, install the `sqlserver` extra and point to an ODBC connection string (requires the appropriate system ODBC driver, e.g. _ODBC Driver 18 for SQL Server_):```bash
pip install "zettelkasten-mcp[sqlserver]"
export ZETTELKASTEN_DATABASE="mssql+pyodbc://user:password@server/database?driver=ODBC+Driver+18+for+SQL+Server"

Using pipx:```bash
pipx install "zettelkasten-mcp[sqlserver]"
export ZETTELKASTEN_DATABASE="mssql+pyodbc://user:password@server/database?driver=ODBC+Driver+18+for+SQL+Server"


Note for container users: SQL Server support is available in the published
Docker image on `linux/amd64` only. On `linux/arm64`, the container does not
include SQL Server ODBC drivers, so use SQLite/PostgreSQL/MySQL instead.

## Usage

### Starting the Server```bash
python -m zettelkasten_mcp

Or with explicit configuration:```bash
python -m zettelkasten_mcp --notes-dir ./data/notes --database ./data/db/zettelkasten.db


Or with PostgreSQL:```bash
python -m zettelkasten_mcp --notes-dir ./data/notes \
  --database postgresql+psycopg://user:password@localhost:5432/zettelkasten

Connecting to Claude Desktop

Using smithery```bash

npx -y @smithery/cli install zettelkasten-mcp --client claude


### Manually

Add the following configuration to your Claude Desktop:```json
{
  "mcpServers": {
    "zettelkasten": {
      "command": "/absolute/path/to/zettelkasten-mcp/.venv/bin/python",
      "args": ["-m", "zettelkasten_mcp"],
      "env": {
        "ZETTELKASTEN_NOTES_DIR": "/absolute/path/to/zettelkasten-mcp/data/notes",
        "ZETTELKASTEN_DATABASE": "postgresql+psycopg://user:password@localhost:5432/zettelkasten",
        "ZETTELKASTEN_LOG_LEVEL": "INFO"
      }
    }
  }
}

Set ZETTELKASTEN_DATABASE to a filesystem path for SQLite or any SQLAlchemy URL (for example PostgreSQL) to choose the backend.

Available MCP Tools

All tools have been prefixed with zk_ for better organization:

Tool Description
zk_create_note Create a new note with a title, content, and optional tags
zk_get_note Retrieve a specific note by ID or title
zk_update_note Update an existing note's content or metadata
zk_delete_note Delete a note
zk_create_link Create links between notes
zk_remove_link Remove links between notes
zk_search_notes Search for notes by content, tags, or links
zk_get_linked_notes Find notes linked to a specific note
zk_get_all_tags List all tags in the system
zk_find_similar_notes Find notes similar to a given note
zk_find_central_notes Find notes with the most connections
zk_find_orphaned_notes Find notes with no connections
zk_list_notes_by_date List notes by creation/update date
zk_rebuild_index Rebuild the database index from Markdown files

Project Structure```

zettelkasten-mcp/
├── src/
│ └── zettelkasten_mcp/
│ ├── models/ # Data models
│ ├── storage/ # Storage layer
│ ├── services/ # Business logic
│ └── server/ # MCP server implementation
├── data/
│ ├── notes/ # Note storage (Markdown files)
│ └── db/ # Database for indexing
├── tests/ # Test suite
├── .env.example # Environment variable template
└── README.md


## Tests

Comprehensive test suite for Zettelkasten MCP covering all layers of the application from models to the MCP server implementation.

### How to Run the Tests

From the project root directory, run:

#### Using pytest directly```bash
python -m pytest -v tests/

Using UV```bash

uv run pytest -v tests/


#### With coverage report```bash
uv run pytest --cov=zettelkasten_mcp --cov-report=term-missing tests/

Running a specific test file```bash

uv run pytest -v tests/test_models.py


#### Running a specific test class```bash
uv run pytest -v tests/test_models.py::TestNoteModel

Running a specific test function```bash

uv run pytest -v tests/test_models.py::TestNoteModel::test_note_validation


### Tests Directory Structure```
tests/
├── conftest.py - Common fixtures for all tests
├── test_integration.py - Integration tests for the entire system
├── test_mcp_server.py - Tests for MCP server tools
├── test_models.py - Tests for data models
├── test_note_repository.py - Tests for note repository
├── test_search_service.py - Tests for search service
├── test_semantic_links.py - Tests for semantic linking
└── test_zettel_service.py - Tests for zettel service

Important Notice

⚠️ USE AT YOUR OWN RISK: This software is experimental and provided as-is without warranty of any kind. While efforts have been made to ensure data integrity, it may contain bugs that could potentially lead to data loss or corruption. Always back up your notes regularly and use caution when testing with important information.

Credit Where Credit's Due

This MCP server was crafted with the assistance of Claude, who helped organize the atomic thoughts of this project into a coherent knowledge graph. Much like a good Zettelkasten system, Claude connected the dots between ideas that might otherwise have remained isolated. Unlike Luhmann's paper-based system, however, Claude didn't require 90,000 index cards to be effective.

License

MIT License

Pre-commit (code formatting)

To keep code style consistent, this project uses pre-commit with black and isort configured.

Install and enable the hooks locally:bash pip install pre-commit pre-commit install pre-commit run --all-files

If you use a virtual environment, make sure the environment is activated before running pre-commit install so the hooks point to the correct Python interpreter.

Editor configuration (VS Code)

This project includes recommended settings for Visual Studio Code to enable automatic import completions and organize imports on save. The workspace settings are in .vscode/settings.json and recommended extensions in .vscode/extensions.json.

Recommended VS Code extensions:

  • ms-python.python — Python language support
  • ms-python.vscode-pylance — Pylance language server (provides auto-import completions)

Important settings (already configured):

  • python.analysis.autoImportCompletions: true — shows auto-import suggestions in completions
  • editor.codeActionsOnSave.source.organizeImports: true — runs import sorting on save
  • editor.formatOnSave: true with Black as the formatter

Activate the workspace settings by opening the project in VS Code; you may need to install the extensions and reload the window.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Zettelkasten MCP 怎么安装?

在客户端按下面的安装命令接入:pip install pre-commit。装完在客户端配置里引用同一个包或端点。

Zettelkasten MCP 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Zettelkasten MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zettelkasten MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Zettelkasten MCP 能提供哪些能力?

资料显示能力标签包括 笔记系统、Python、知识管理、文档处理。具体工具清单以官方文档为准。

Zettelkasten MCP 需要什么运行环境?

运行时为 Python。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。