SiYuan Note MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIYUAN_TOKEN | Yes | 思源笔记 API 令牌（必需）| SiYuan Note API token (required) - 在思源笔记设置 - 关于 中查看 | Check in SiYuan Note Settings - About - 用于 API 认证 | Used for API authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| executeCommandD | 执行指定的命令 |
| queryCommandsA | 查询可用的命令列表 |
| helpB | 获取命令的帮助信息 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: executeCommand performs actions, help provides documentation, and queryCommands lists available commands. There is no overlap in functionality, making it easy for an agent to select the correct tool for each task.
The tool names follow a consistent verb_noun pattern (executeCommand, queryCommands) with one minor deviation (help is a noun-only name). This small inconsistency does not significantly impact readability or predictability, as the naming is still clear and logical.
With only 3 tools, the server feels thin for a note-taking domain, as it lacks operations for creating, reading, updating, or deleting notes directly. While the tools provide a command-based interface, the count is borderline low for the apparent scope of managing notes in SiYuan.
The tool surface is significantly incomplete for a note-taking server. There are no tools for core CRUD operations on notes (e.g., create_note, get_note, update_note, delete_note), which are essential for agent workflows. The current tools only support command execution and help, leaving major gaps in functionality.