An MCP server for siyuan-note

中文

A plugin that provides MCP service for Siyuan Note.

🌻 Features

• Most tools support the exclude document function.

• It includes certain input parameter validation and is not a direct API wrapper for SiYuan Note.

• Ready to use once the plugin is installed and enabled on the desktop client; Docker and mobile platforms are not supported.

Related MCP server: MCP Apple Notes

✨ Quick Start

• Download from the marketplace or 1. unzip the package.zip in Release, 2. move the folder to workspace/data/plugins/, 3. and rename the folder to syplugin-anMCPServer;

• Enable the plugin;

• The plugin listens on port 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!

🔧 Supported Tools

❓ Frequently Asked Questions

• Q: How to use in an MCP client?

  • Please refer to the sections below.

• Q: What are common MCP clients?

  • Please refer to: https://github.com/punkpeye/awesome-mcp-clients or https://modelcontextprotocol.io/clients.

• Q: Does the plugin support authentication?

  • Authentication is supported since v0.2.0. After setting an auth token in plugin settings, you must set the authorization request header in your MCP client with value: Bearer {YourToken}.

• Q: Can it be used in Docker?

  • No. The plugin depends on the Node.js environment and does not support running on mobile or in Docker.

    If you need to support SiYuan deployed in Docker, it is recommended to use other MCP projects. Some may be listed here.

    Alternatively, modify the code to decouple this plugin from the SiYuan frontend.

• Q: How to view the set authorization token?

  • The token is stored hashed. It can only be modified, not viewed in plaintext while active.

• Q: I only connected once, why does the connection count on the settings page show more than 1?

  • Outdated statistics: Please manually click Refresh Status to get the latest result.

  • Connections not fully released: Some MCP clients do not send a standard disconnect signal on close, leaving old connections alive in the background. New connections are added when the feature is restarted.

  • Multi-device connections: Please confirm whether other software is accessing the MCP service or related ports.

  • Still having issues? Check the plugin logs or set an authorization token to prevent information leakage.

• Q: What is the "Vector Search Client Plugin - Query" tool?

  • This tool retrieves matching content blocks or answers questions directly via knowledge graph / vector search.

  • To use it, you must first download, enable, and properly configure the syplugin-vectorIndexClient plugin.

  • Currently, this plugin only supports lightRAG-server.

How to Configure in an MCP Client?

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 is abcdefg.

Modify the MCP application’s configuration, select the Streamable HTTP type, and configure the endpoint.

Clients Supporting Streamable HTTP

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

1. Type: Select Streamable HTTP (streamablehttp);

2. URL: http://127.0.0.1:16806/mcp;

3. Headers: Leave empty;

Plugin With Authorization Token

1. Type: Select Streamable HTTP (streamablehttp);

2. URL: http://127.0.0.1:16806/mcp;

3. Headers: Authorization=Bearer abcedfg;

Clients Supporting Only Stdio

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.

1. Download Node.js: https://nodejs.org/en/download

2. 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

🙏 References & Acknowledgements

Some dependencies are listed in package.json.