vicky

Vicky

Demand-driven knowledge base MCP server. Auto-enriches answers when gaps detected. Drives Obsidian + Dataview for live KB views.

What it does

• Install, run /vicky:learn, watch your KB grow automatically. Tier-progressive, fully hands-off.
• Local KB of sources + conclusions, queried by your agent
• Detects gaps in your question, auto-enqueues research
• Processes the queue automatically (monitors + tier progression, no manual intervention)
• Enriches conclusions via research, synthesis, and cross-linking
• Exposes Dataview (DQL) directly to the agent for arbitrary KB queries
• Ships an Obsidian vault preset (Dataview pre-configured)

Requirements

• Node.js 18+
• Obsidian (for dashboard / dql tools)
• Any MCP-capable agent (Claude Code, Claude API, Cursor, etc.)
• LLM API key for graphify's semantic pass (see LLM API key below)

graphify ships as a bundled dependency (graphifyy on npm). npm install pulls it in — no external install needed. Vicky resolves the local binary at runtime.

Install

Claude Code (plugin)

/plugin marketplace add yesitsfebreeze/vicky
/plugin install vicky@vicky

Registers the MCP server, hooks init() to SessionStart, and exposes the vicky skill. First session scaffolds the Obsidian preset (.obsidian/ with Dataview + graph) at the project root and vicky/{sources,conclusions,pending,graphs,Dashboard.md,WORKFLOW.md} beside it. The project root is the Obsidian vault.

Any other MCP-capable agent

git clone https://github.com/yesitsfebreeze/vicky ~/vicky
cd ~/vicky/src && npm install && npm run build

Register the MCP server pointing at ~/vicky/dist/index.js. Example .mcp.json:

{
  "mcpServers": {
    "vicky": {
      "command": "node",
      "args": ["~/vicky/dist/index.js"]
    }
  }
}

Restart the agent. First call triggers init(). Open the project root in Obsidian — the .obsidian/ preset enables Dataview + graph settings. (Plugins must be installed via the Community Plugins UI on first run; the preset only declares which are enabled.)

Update

cd ~/vicky && git pull && cd src && npm install && npm run build

Restart the agent so the MCP server reloads. vicky/ is yours — init() never overwrites existing files.

Tools (MCP)

Tool	Purpose
research-gap "q"	Query KB; auto-enqueue if gap
research	Fetch sources, call learn (tier-progressive, sets up monitors)
learn [tier] [count]	Tier-progressive: drain pending by importance, relink, create file monitors
query "q"	Direct KB lookup (focus-biased)
remember "title"	Save findings to vault
enqueue "q"	Manual queue add
dashboard	KB report via Obsidian + Dataview
dql "<query>"	Run arbitrary DQL. query="help" for syntax
relink	Rebuild link graph
web-search	Web research helper

File Monitors (Claude Code)

When you run /vicky:learn, it instructs Claude Code to create monitors on dependent files:

• .graphify/graph.json changes → auto-run /vicky:relink (refresh links)
• .graphify/.graphify_ast.json changes → auto-run /vicky:learn (re-analyze importance)
• pending/ grows → auto-run /vicky:learn (drain queue)
• sources/ changes → auto-run /vicky:relink (update graph)

No periodic polling needed — reactions trigger instantly when files change. Manage monitors with /monitor list, /monitor pause vicky/, /monitor delete vicky/.... See MONITORS.md for details.

Layout

~/vicky/                     # plugin root (clone target)
├── .claude-plugin/          # plugin manifest
├── hooks/                   # SessionStart init hook
├── dist/                    # bundled MCP server (CI-built, committed)
├── scaffold/                # template tree mirroring project root (copied to . on init)
├── skills/                  # Claude Code skills
├── src/                     # source + build (node_modules lives here)
│   ├── package.json
│   ├── build.js
│   ├── index.js, init.js, dashboard.js, ...
│   └── tools/
└── README.md                # this file