SiYuan Note MCP
STDIOHTTP-SSEA plugin that provides MCP service for Siyuan Note.
A plugin that provides MCP service for Siyuan Note.
A plugin that provides MCP service for Siyuan Note.
Current Version: v0.2.0 (This version contains breaking changes)
Improvements:
Added support for Streamable HTTP connections (endpoint changes required)Marked SSE connection as deprecated (will be removed in future versions) - Please reconfigure according to documentation
Different devices can now use separate config files - Note: Upgrading will reset existing configurations
New Feature:
Added access authorization code support
package.zip
in Release, 2. move the folder to workspace/data/plugins/
, 3. and rename the folder to syplugin-anMCPServer
;16806
by default (Host: 127.0.0.1
), please use http://127.0.0.1:16806/sse
as the server access address;⭐ If this is helpful to you, please consider giving it a star!
Q: How to use it in an MCP client?
Please refer to the later sections;
Q: What are some common MCP clients?
Q: Does the plugin support authentication?
authorization
request header with the value Bearer YourToken
;Q: What is the connection count?
Q: Can it be used in Docker?
No, the plugin relies on a Node.js environment and does not support running on mobile devices or Docker.
To support SiYuan deployed in Docker, it is recommended to switch to other MCP projects. Some relevant projects may be listed here.
Alternatively, decouple this plugin from the SiYuan frontend.
Different MCP clients require different configuration methods. Please refer to the MCP client documentation.
MCP clients are continuously updated, so the configuration or usage instructions here may not be directly applicable and are for reference only.
Here, we assume: the plugin’s port is
16806
, and the authorization token isabcdefg
.
Modify the MCP application’s configuration, select the Streamable HTTP
type, and configure the endpoint.
The following configuration uses Cherry Studio as an example. Different MCP clients may require different configuration formats—please refer to the MCP client documentation.
Plugin Without Authorization Token
streamablehttp
);http://127.0.0.1:16806/mcp
;Plugin With Authorization Token
streamablehttp
);http://127.0.0.1:16806/mcp
;Authorization=Bearer abcedfg
;If the MCP client does not support HTTP-based communication and only supports stdio, a conversion method is needed.
Here, we use node.js
+ mcp-remote@next
.
Download Node.js: https://nodejs.org/en/download
Install mcp-remote@next
:
npm install -g mcp-remote@next
The following configuration uses 5ire as an example. Different MCP clients may require different configuration formats—please refer to the MCP client documentation.
Plugin Without Authorization Token
Command:
npx mcp-remote@next http://127.0.0.1:16806/mcp
Plugin With Authorization Token
Command:
npx mcp-remote@next http://127.0.0.1:16806/mcp --header Authorization:${AUTH_HEADER}
Environment Variable:
Name: AUTH_HEADER
Value: Bearer abcdefg
Some dependencies are listed in
package.json
.
Developer/Project | Project Description | Citation |
---|---|---|
thuanpham582002/tabby-mcp-server | Provides MCP service within the terminal software Tabby; MIT License | Implementation method of MCP service |