Vault Knowledge

com.seanwinslowPublished by seanwinslow.comv0.1.0Updated Oct 24, 2026

Read-only MCP over a vault's typed knowledge graph: concept search, contradictions, article fetch.

VerifiedSTDIODesktop onlyFiles & StorageKnowledge & Memory

Overview

AI-generated overview

A read-only local MCP server that exposes an Obsidian vault's typed knowledge graph, letting an assistant search concepts, find contradictions and fetch notes.

What you can do
Search concept and connection articles in the vault with semantic ranking and a result limit, and find active contradiction edges across the whole graph or the last 30 days, and fetch a single article by slug with its frontmatter, body and resolved wikilinks.
When to use it
Useful when your notes live in an Obsidian vault and you want an assistant to look things up, trace how ideas connect, or point out where your own notes disagree. It ships with a sample vault, so it can be tried before pointing it at real notes.
Requirements
Runs locally over stdio via npx, so Node 22.5 or newer is needed for the built-in SQLite module. To use your own vault, set the VAULT_DB and VAULT_ROOT environment variables to an index database and vault path. The first concept search downloads the nomic-embed-text-v1.5 model. No authentication or cloud service.
Before you install
Read-only by design, with access limited to the knowledge concepts, connections and qa folders, and scope fixed by configuration rather than per request. The first search downloads an embedding model over the network. Point VAULT_ROOT only at a vault you are comfortable exposing to the assistant.

Installation

In SourceWeft

  1. Open Vault Knowledge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

vault-knowledge-mcp

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.

Tools

ToolReturns
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.

Try it — zero config

Ships with a synthetic espresso vault, so it works the moment it installs.

json
{  "mcpServers": {    "vault-knowledge": { "command": "npx", "args": ["-y", "@swins/vault-knowledge-mcp"] }  }}

Then ask: "find contradictions in the vault."

Point it at your own vault

json
{  "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.

Requirements

Node ≥ 22.5 (built-in node:sqlite). search_concepts downloads the nomic-embed-text-v1.5 model once on first run.

License

MIT.

Source: README.md at commit fc83a14

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts