siyuan-note-mcp
Related Servers
Alternatives to siyuan-note-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to read, search, and write SiYuan notes through standard MCP tools, with read and write operations and secure authentication.69 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server for SiYuan Note that enables comprehensive management of notebooks, documents, and blocks through AI integration. It supports advanced operations like SQL querying, OCR, multi-format exports, and automated content searching for intelligent knowledge management.37 npm5-
- FlicenseNot gradedqualityBmaintenanceEnables managing SiYuan notes via MCP: search, browse, read, and write Markdown notes with automatic bi-directional links, while restricting write/delete operations to a designated writable notebook.-
- AlicenseNot gradedqualityDmaintenanceProvides a local MCP stdio server that enables AI clients to read, search, create, update, and delete notes in SiYuan through its Kernel HTTP API, with configurable notebook and tool permissions.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude and Cursor to interact seamlessly with SiYuan Note through 15 specialized tools. It supports comprehensive note operations including unified search, document management, daily notes, and tag manipulation.43 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for SiYuan Note, enabling AI integration and smart knowledge management with note, block, search, template, export, asset, SQL, and file operations.37 npmMIT
TDQS
Scored across 13 tools
Most tools target distinct resource+action pairs and descriptions explicitly distinguish reading vs editing. However, delete_block (which can delete a whole document) overlaps with remove_document, and get_document vs get_block require reading descriptions to separate. These are minor and well-clarified.
Nearly every tool follows a clean verb_noun pattern (list_notebooks, get_document, insert_block, update_block, delete_block, create_document, rename_document, remove_document, move_document). The only outlier is sql_query, which is a conventional, idiomatic exception.
13 tools is well within the ideal range and each earns its place across document, block, search, and query operations. No redundant or filler tools.
Document lifecycle (create/read/rename/move/remove) and block CRUD (get/insert/update/delete) are fully covered, plus search and SQL escape hatch. The main gap is notebook-level management — notebooks can only be listed, not created/renamed/deleted.