MCP Server with SSE endpoint for Obsidian
LocalAbout MCP Server with SSE endpoint for Obsidian
This is an MCP server with an SSE endpoint for Obsidian, used to connect an Obsidian vault to self-hosted n8n. The Obsidian API must be installed in the vault before running it.
Key features
- 01SSE endpoint for Obsidian
- 02Connects a vault to self-hosted n8n
- 03Based on the mcp-server project
Use cases
- 01Connect an Obsidian vault to self-hosted n8n
- 02Connect MCP clients to Obsidian over SSE
MCP support
The MCP server provides an SSE endpoint for clients to connect to an Obsidian vault. The README does not specify its tools or resources.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP Server with SSE endpoint for Obsidian
This is a simple MCP server with a SSE endpoint for Obsidian. I use this to connect my obsidian vault to my self-hosted n8n. Before running this, you need to install the Obsidian API on your obsidian vault.
Usage
git clone https://github.com/mcp-server/mcp-obsidian-sse.git
uv --directory mcp-obsidian-sse uvicorn main:app --reload
Credit
This project is based on the mcp-server project.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.