Semantic MCP server for Obsidian - AI-optimized interface with 5 intelligent operations
Connect Obsidian Semantic MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Semantic MCP server for Obsidian - AI-optimized interface with 5 intelligent operations. The obsidian semantic mcp mcp server is what makes that connection.
A semantic, AI-optimized MCP server for Obsidian that consolidates 20 tools into 5 intelligent operations with contextual workflow hints.
The server ships on npm as obsidian-semantic-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Configuration — The semantic workflow hints are defined in src/config/workflows.json and can be customized for your workflow preferencesArchitecture — The Architecture tool exposed by this serverTesting — The project includes comprehensive Jest tests for the semantic system:Configuration is passed through the environment: OBSIDIAN_API_KEY, OBSIDIAN_API_URL, OBSIDIAN_VAULT_NAME. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
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 Semantic MCP's toolset — Configuration, Architecture, Testing — is a fair guide to whether it matches your workflow. It is maintained by aaronsb; 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 |
|---|---|
| Configuration | The semantic workflow hints are defined in src/config/workflows.json and can be customized for your workflow preferences. |
| Architecture | The Architecture tool exposed by this server. |
| Testing | The project includes comprehensive Jest tests for the semantic system: |
{
"mcpServers": {
"obsidian-semantic": {
"command": "npx",
"args": ["-y", "obsidian-semantic-mcp"],
"env": {
"OBSIDIAN_API_KEY": "your-value",
"OBSIDIAN_API_URL": "your-value",
"OBSIDIAN_VAULT_NAME": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OBSIDIAN_API_KEY | Credential the server authenticates with. | Yes |
| OBSIDIAN_API_URL | Endpoint or connection string the server talks to. | Yes |
| OBSIDIAN_VAULT_NAME | Configuration value read at startup. | 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.