Skip to main content
Glama
leolulu

siyuan-mcp-server

by leolulu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to siyuan-mcp-server

No user-submitted related servers found.

    Related Servers

    • SiYuan MCP Server

      rexding97
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to create, read, update, and manage SiYuan notes, supporting notebook management, document operations, block editing, database attribute views, search, file operations, and export.
      11
      19 npm
      1
      MIT

    • SiYuan MCP Server

      xgq18237
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to interact with SiYuan Note through its API, supporting notebook and document management, block operations, search, file operations, and more.
      69
      82 npm
      72
      MIT

    • siyuan-mcp

      remixu1994
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to read, search, and write SiYuan notes through standard MCP tools, with read and write operations and secure authentication.
      82 npm
      MIT

    • SiYuan Note MCP Server

      Fromsko
      A
      license
      C
      quality
      B
      maintenance
      Enables AI assistants to interact with SiYuan Note for comprehensive notebook management, document editing, and block-level content operations. It supports advanced features like full-text search and SQL queries via secure API integration.
      3
      20 npm
      40
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and the descriptions explicitly clarify differences between lookalike pairs like insert_block vs append_block/prepend_block and get_block_changes vs get_block_diffs. However, get_file vs get_history_file are explicitly described as behaving the same way, and list_files vs list_history_entries overlap for history-directory exploration.

    Naming Consistency4/5

    The overall pattern is consistent snake_case verb_noun naming (get_block, create_document, delete_block, move_block). Minor inconsistencies exist, such as mixing 'find_' and 'search_' for similar query operations and the awkward plural 'get_blocks_content'.

    Tool Count3/5

    22 tools is on the heavy side for an MCP server and includes some redundancy in file/history access (get_file, get_file_base64, get_history_file, list_history_entries). The count is not unmanageable, but several tools could be consolidated without losing core functionality.

    Completeness3/5

    Block-level CRUD is well covered, and document creation/finding plus history querying provide useful workflows. However, document lifecycle coverage is incomplete: there is no way to update, rename, move, or delete a document, and notebook management is limited to discovery only.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources