Read-only MCP over a vault's typed knowledge graph: concept search, contradictions, article fetch.
A read-only MCP server that turns an Obsidian vault's typed knowledge graph into three tools any MCP client can call. Most knowledge tools can search. Few can tell you where your own notes disagree with each other. This one traverses a six-relation reasoning graph and surfaces the sharpest edge — contradicts. Local-first, stdio, no auth, no cloud, no native build.
The full reasoning lives in docs/EXPLANATION.md.
| Tool | Returns |
|---|---|
search_concepts(query, limit=5) | Semantically ranked concept/connection articles. |
find_contradictions(scope='all'|'recent_30d') | Active contradicts edges from the reasoning graph. |
get_article(slug) | One article with frontmatter, body, and resolved wikilinks. |
Ships with a synthetic espresso vault, so it works the moment it installs.
{
"mcpServers": {
"vault-knowledge": { "command": "npx", "args": ["-y", "@swins/vault-knowledge-mcp"] }
}
}
Then ask: "find contradictions in the vault."
{
"mcpServers": {
"vault-knowledge": {
"command": "npx",
"args": ["-y", "@swins/vault-knowledge-mcp"],
"env": {
"VAULT_DB": "/abs/path/.vault-index.db",
"VAULT_ROOT": "/abs/path/vault"
}
}
}
}
Only knowledge/{concepts,connections,qa} is ever readable. Scope is config-only — never a request parameter, so a client can't widen it.
Node ≥ 22.5 (built-in node:sqlite). search_concepts downloads the nomic-embed-text-v1.5 model once on first run.
MIT.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @swins/vault-knowledge-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-seanwinslow-vault-knowledge": {
"command": "npx",
"args": [
"-y",
"@swins/vault-knowledge-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@swins/vault-knowledge-mcpnpmcom.seanwinslow/vault-knowledge works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.