Obsidian Knowledge-Management MCP (Model Context Protocol) server that enables AI agents and development tools to interact with an Obsidian vault. It
Obsidian Enhanced MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Obsidian Knowledge-Management MCP (Model Context Protocol) server that enables AI agents and development tools to interact with an Obsidian vault. It provides a comprehensive suite of tools for reading, writing, searching, and managing.
An MCP (Model Context Protocol) server providing comprehensive access to your Obsidian vault. Enables LLMs and AI agents to read, write, search, and manage your notes and files through the Obsidian Local REST API plugin.
The Obsidian MCP Server acts as a bridge, allowing applications (MCP Clients) that understand the Model Context Protocol (MCP) – like advanced AI assistants (LLMs), IDE extensions, or custom scripts – to interact directly and safely with your Obsidian vault.
Once Obsidian Enhanced is connected, these are the calls the assistant has available:
Case — insensitive path fallbackPrerequisites — The Prerequisites tool exposed by this serverInstallation — 1. Clone this enhanced repository: bash git clone https://github.com/BoweyLou/obsidian-mcp-server-enhanced.git cd obsidian-mcp-server-enhanced 2Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 8 environment variables: MCP_AUTH_KEY, OBSIDIAN_API_KEY, OBSIDIAN_BASE_URL, OBSIDIAN_VAULTS, OBSIDIAN_ENABLE_CACHE, CHATGPT_FACADE_PUBLIC_URL, CHATGPT_FACADE_ADMIN_SECRET, MCP_HTTP_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Obsidian Enhanced's toolset — Case, Prerequisites, Installation — is a fair guide to whether it matches your workflow. It is maintained by BoweyLou; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Case | insensitive path fallback. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | 1. Clone this enhanced repository: bash git clone https://github.com/BoweyLou/obsidian-mcp-server-enhanced.git cd obsidian-mcp-server-enhanced 2. Install dependencies: bash npm install 3. Build the project: bash npm run |
{
"mcpServers": {
"obsidian-mcp-server": {
"command": "node",
"args": ["/path/to/your/obsidian-mcp-server-enhanced/dist/index.js"],
"env": {
"MCP_AUTH_KEY": "your-generated-mcp-auth-key",
"OBSIDIAN_API_KEY": "your-obsidian-api-key",
"OBSIDIAN_BASE_URL": "http://127.0.0.1:27123",
"OBSIDIAN_ENABLE_CACHE": "true"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MCP_AUTH_KEY | Credential the server authenticates with. | Yes |
| OBSIDIAN_API_KEY | Credential the server authenticates with. | Yes |
| OBSIDIAN_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| OBSIDIAN_VAULTS | Configuration value read at startup. | Optional |
| OBSIDIAN_ENABLE_CACHE | Configuration value read at startup. | Optional |
| CHATGPT_FACADE_PUBLIC_URL | Endpoint or connection string the server talks to. | Yes |
| CHATGPT_FACADE_ADMIN_SECRET | Credential the server authenticates with. | Yes |
| MCP_HTTP_HOST | Endpoint or connection string the server talks to. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.