Skip to content

MCP Vault Server

mcp-vault-server/ provides 15 tools for real-time Obsidian vault integration via the Model Context Protocol.

Obsidian Vault as Fund Knowledge Base

Transport

  • Protocol: MCP over stdio
  • REST API: HTTP on 127.0.0.1:3001 (configurable via MCP_VAULT_API_PORT)
  • Vault path: ~/FundAdmin-AI-Vault/ (direct filesystem access — no REST auth, no network dependencies)

Both the MCP stdio transport and the HTTP API run in a single process (index.js).

Install

bash
claude mcp add fundadmin-vault -s user node mcp-vault-server/index.js

MCP Tools (15)

ToolDescription
vault_write_reviewCreate review with frontmatter including investors: field
vault_add_kanban_cardAdd card to a Kanban board
vault_close_reviewMark review as completed
vault_archive_reviewsQuarterly archival of completed reviews
vault_move_kanban_cardMove card between Kanban columns
vault_review_statusList reviews by status
vault_read_investorRead investor note
vault_list_fundsList all funds with frontmatter
vault_query_trackerQuery tracker registries by fund/investor
+ 6 additional toolsWire, compliance, obligation, performance tracking

REST API Endpoints

The HTTP server on port 3001 provides:

  • POST /api/review/status — update review status
  • POST /api/kanban/add — add Kanban card
  • POST /api/kanban/move — move Kanban card
  • GET /api/kanban/check — check card existence

Review Lifecycle

new → under-review → action-required → completed → archived

Status is tracked via YAML frontmatter status: field in each review file.

Watcher

mcp-vault-server/watcher.js handles:

  • PDF classification (filename + magic-byte content sniff)
  • Non-LPA document archiving (10-K reports, bank statements, IRS forms → Archive/_NonFundDocuments/)
  • Post-review tracking pipeline (8 hooks chained automatically)

Post-Review Hooks

After each review, the watcher automatically chains:

  1. wire-registry.js + wire-extractor.js — wire instruction change detection
  2. capital-tracker.js — cumulative capital calls, distributions, unfunded commitments
  3. compliance-tracker.js — risk flag extraction with macOS notifications for High Risk
  4. investor-tracker.js — LP registry with cross-fund exposure tracking
  5. obligation-tracker.js — side letter obligation deadlines
  6. performance-tracker.js — fund performance snapshots
  7. auto-reconcile.js — detects reconcilable document pairs
  8. skill-chains.js — suggests next /fund commands based on document type
  9. json-sidecar.js — writes .json alongside each .md review

Inbox Watcher (Worker)

apps/worker/src/inbox-watcher.ts runs on a 30-second tick inside the background worker process. It:

  1. Scans ~/FundAdmin-AI-Vault/Inbox/ for LPA files not yet reviewed
  2. Calls /api/review/trigger on the webapp
  3. The webapp runs apps/web/src/lib/review-pipeline.ts (Anthropic SDK, not claude CLI)
  4. Review markdown lands in vault; status flips pending → reviewed

The mcp-vault-server/watcher.js handles classification, archiving, and post-review tracking for non-LPA document types.

Additional Registry Modules

Populate with node mcp-vault-server/<module>.js --populate:

ModulePurpose
kyc-tracker.jsKYC/AML document collection per investor
covenant-tracker.jsDebt covenant compliance with threshold proximity
regulatory-tracker.jsRegulatory filing calendar with deadline tracking
mfn-tracker.jsMFN election tracking with cascade risk analysis

Obsidian Vault Structure

/fund vault-init creates ~/FundAdmin-AI-Vault/ with:

  • 7 Dataview-powered dashboards
  • 9 Kanban boards
  • 7 templates (daily/weekly/monthly/quarterly)
  • 3 Metadata Menu FileClasses (Fund, Investor, Review)
  • 12 review subfolders

T1 (skills + CLI) and T2 (vault template) are MIT licensed.