SiYuan Sisyphus MCP

An MCP server and CLI for SiYuan notes with notebook-level permissions, rollback of agent edits and a document timeline.

  • 123 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • The agent writes to SiYuan notes and at the `rwd` level can delete documents.
  • Native SiYuan and other-plugin tools are not bound by Sisyphus permissions.
All reasons and checks

yangtaihong59/siyuan-plugins-mcp-sisyphus

Install

Manual install

npm i -g siyuan-sisyphus

Installs the CLI. The plugin itself comes from the SiYuan marketplace, and `siyuan-sisyphus init` sets the API URL and token.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The agent writes to SiYuan notes and at the `rwd` level can delete documents.
  • Native SiYuan and other-plugin tools are not bound by Sisyphus permissions.

This is third-party code. Review the repository files before installing.

What it does

SiYuan Sisyphus lets an agent work in SiYuan notes only where it is allowed. More than a hundred SiYuan capabilities sit behind 14 action-routed tools, and detailed help and skills load on demand to keep context small. Paths like `/Notebook/Project/Note` spare the agent block IDs. Each notebook gets a `none`, `r`, `rw` or `rwd` level, and delete, move and replace have their own switches. A write is checked against the target current-state hash, committed once and read back. Before the agent starts, you can create a timeline node, compare it with the document and roll back the whole document or a single block. MCP Apps open flashcard review, the timeline and a mascot shop inside the conversation, and a human makes the final call. The `siyuan-sisyphus` CLI runs the same tools from a terminal.

Who it is for. SiYuan users who keep working notes there and want to give an agent restricted access with a way to roll back.

Good fit when

  • An agent tidies a weekly review and its edits must be reviewed block by block.
  • One notebook is read-only, another writable and a third closed.
  • A terminal script needs the notebook list as JSON.
  • An agent needs SiYuan markup help that should not sit in context all the time.

Not a fit when

  • SiYuan is older than 2.9.0, where the plugin will not run.
  • The agent should get the whole workspace, native SiYuan tools included, without limits.
  • Notes live in another application.

Example request

List my SiYuan notebooks and find notes about the weekly review without changing anything.

MCP

Transport
http, stdio
Authentication
API key

Limitations

The plugin runs on SiYuan 2.9.0 and newer, while the official MCP bridge and the kernel endpoint need 3.7.0. Notebooks without a settings entry are read-only, but notebooks created after installation start at `rwd`, so review the levels before the first request. Tools from other plugins and native SiYuan tools bypass Sisyphus permissions, so enable native ones only for local trusted clients. The timeline relies on workspace snapshots and does not replace Git.

How to disable. Disable the plugin in SiYuan settings and remove the MCP entry from the client. Uninstall the CLI with `npm uninstall -g siyuan-sisyphus`.

FAQ

How do I connect SiYuan Sisyphus to Claude Code?

Install the plugin from the SiYuan marketplace, open its settings, go to the MCP connection section, pick a client and transport and copy the generated configuration. Presets exist for Claude Code, Codex CLI, Cursor and OpenCode.

What can the agent do to a notebook?

The notebook level decides: `none` blocks, `r` reads, `rw` writes and `rwd` also deletes. Delete, move and replace require confirmation.

How do I roll back agent edits?

Create a timeline node before work starts, compare it with the document and restore the whole document or a single block. Rollback is disabled for AI by default.

How does the CLI differ from MCP?

They share one core. MCP suits agents chaining multi-step work, while the CLI fits scripts and one-shot tasks and keeps tool schemas out of the context.

Which SiYuan version is required?

The plugin runs on SiYuan 2.9.0 and newer. The official MCP bridge and the kernel endpoint need 3.7.0.

Discussion

No questions or reviews yet.

Official

A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes

MCP serverExtended access47.2KRepository stars

Terminal notes, tasks and a Kanban board over plain markdown files, with a JSON CLI and an MCP server for agents.

CLIMinimal access102Repository stars

The MCP endpoint of a Salt workspace on your server: an agent creates pages, databases and comments with a person rights.

MCP serverBroad access178Repository stars

An MCP server for Feishu and Lark: the agent reads and edits documents block by block, manages tasks and finds colleagues, with the same tools as a CLI

MCP serverBroad access750Repository stars

An MCP server and Mac app that keeps one local index of repos, agent sessions and tickets, with semantic search and work threads

MCP serverExtended access76Repository stars
Official

Automattic's official Simplenote MCP server: an agent reads, searches and optionally edits notes, with no sign-in on macOS

MCP serverExtended access33Repository stars

README in short

The project is heading toward compatibility with the official SiYuan MCP and simple setup in popular agents. Bugs can be reported in Issues or through the built-in `feedback` tool.

README badge

Report a problem