vestige/crates/vestige-mcp
Claude e89a922cf8
docs: fix v2.2.0 drift and purge private content
Drift corrections:
- server.rs: advertised-tool comment 12 -> 13 (matches the code + test)
- crates/vestige-mcp/README.md: replace stale pre-consolidation tool
  list with the real 13 advertised tools + hidden-alias note
- tool-consolidation-v2.2.0.md: reconcile 12 (fold) vs 13 (fold +
  net-new backfill), matching test_tools_list_returns_all_tools
- VESTIGE_STATE_AND_PLAN.md: current release shape v2.1.21 -> v2.2.0
- CONFIGURATION.md: stale --version example -> v2.2.0
- README.md / CONTRIBUTING.md: LOC 86,000+ -> 92,000+, binary 22MB -> 23MB
  (test badge 1,550 verified accurate via full suite: 1550 passed / 0 failed)

Private content removed:
- marketing/funding collateral (docs/launch/{blog-post,demo-script,
  show-hn,opencode-adoption,reddit-cross-reference}, demo pitch/funding files)
- unshipped-cloud planning cluster (docs/plans, docs/prd, docs/adr) which
  carried real private local paths and machine names
- README: repoint a broken/private demo link to the public demo

Kept public: demo/README.md + postdict-demo.sh, tool-consolidation doc,
blackbox-proof pack. Guard (check-no-private-cloud) passes; no private
path markers remain; no broken cross-references.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B3RxH4JxAQYsuA9kFVnR5v
2026-07-01 15:03:47 +00:00
..
src docs: fix v2.2.0 drift and purge private content 2026-07-01 15:03:47 +00:00
Cargo.toml chore(release): v2.2.0 — Retroactive Salience + Tool Consolidation 2026-06-29 15:15:54 -05:00
README.md docs: fix v2.2.0 drift and purge private content 2026-07-01 15:03:47 +00:00

Vestige MCP Server

Local cognitive memory for MCP-compatible AI agents.

This crate provides the vestige-mcp stdio MCP server plus the vestige CLI. The cognitive engine lives in vestige-core; this crate owns protocol handling, tool dispatch, optional dashboard serving, backups, restore, update, and portable import/export commands.

Install

For normal users, prefer the release package:

npm install -g vestige-mcp-server

For local development:

cargo build --release -p vestige-mcp

Register With An MCP Client

Use the command vestige-mcp in any stdio MCP client:

{
  "mcpServers": {
    "vestige": {
      "command": "vestige-mcp"
    }
  }
}

Examples:

claude mcp add vestige vestige-mcp -s user
codex mcp add vestige -- vestige-mcp

Transports

  • Default: JSON-RPC 2.0 over stdio.
  • Optional: MCP-over-HTTP on /mcp, enabled only with --http, --http-port, or VESTIGE_HTTP_ENABLED=1.
  • Dashboard: vestige dashboard or VESTIGE_DASHBOARD_ENABLED=1.

HTTP and dashboard bearer tokens are generated locally; see docs/CONFIGURATION.md.

Current Tool Surface

As of v2.2, the server advertises 13 consolidated tools from src/server.rs:

  • recall — unified retrieval (folds search + deep_reference + cross_reference + contradictions); modes lookup/reason/contradictions
  • smart_ingest — Prediction-Error-gated ingestion (single + batch)
  • memory — get / edit / promote / demote / state / purge
  • graph — chains, associations, bridges, predictions, force-directed export (folds explore_connections + predict + memory_graph + composed_graph)
  • maintain — consolidate / dream / gc / importance_score / backup / export / restore
  • dedup — scan / plan_merge / plan_supersede / apply / undo / protect / policy (folds find_duplicates + the 7 Phase-3 merge tools)
  • memory_status — health / retention / timeline / changelog (folds system_status + memory_health + memory_timeline + memory_changelog)
  • suppress — top-down active forgetting (Anderson 2025 + Davis Rac1)
  • backfill — Retroactive Salience Backfill (Cai 2024 Nature), the flagship
  • codebase — per-project patterns and decisions
  • intention — set / check / update / list future triggers
  • source_sync — external-source connectors (GitHub, Redmine)
  • session_start — one-call session initialization (renamed from session_context)

The ~22 pre-consolidation names (search, deep_reference, dream, consolidate, memory_graph, …) still work as hidden back-compat aliases dispatched in handle_tools_call, so existing configs keep working.

See the root README.md and docs/AGENT-MEMORY-PROTOCOL.md for agent instructions.

License

AGPL-3.0-only