Obsidian MCP
Obsidian MCP servers can read, write, search, and link notes in personal knowledge vaults — agents could access private notes and research.
N/A
Could not evaluate
Could not establish a plain stdio MCP session for target `obsidian-mcp`.
Command: npx -y obsidian-mcp
Diagnosis: The process exited or detached before MCP initialization completed.
Raw error: MCP error -32000: Connection closed
Likely causes:
- The package may expect extra startup arguments or environment variables.
- The package may not behave like a plain local-process stdio target under this invocation.
- The server may be crashing immediately and only leaving clues on stderr.
Next steps:
- Run the command manually and look for usage output, auth prompts, or crash text.
- Check whether the package expects a different transport or an app-oriented startup flow.
- Use the recent stderr lines below before assuming this is a harness bug.
Recent stderr:
- obsidian-mcp /tmp/vault # ❌ System directory
- obsidian-mcp ~/.config/vault # ❌ Hidden directory
- obsidian-mcp //server/share/vault # ❌ Network path
- obsidian-mcp /mnt/network/vault # ❌ Network mount
- obsidian-mcp ~/symlink-to-vault # ❌ External symlink
Check Results
0 pass
0 fail
0 partial
3 skipped
tools
Skipped
Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
prompts
Skipped
Skipped because startup failed before the MCP session initialized. See the failure diagnosis.
resources
Skipped
Skipped because startup failed before the MCP session initialized. See the failure diagnosis.