MCP Server

SwarmVault can expose a vault as a local MCP server with:

swarmvault mcp

The current release uses stdio transport and is meant for local agent and tooling integrations.

Why MCP Matters

MCP lets a compatible client treat the vault as a structured tool surface instead of a pile of files. That means an agent can:

  • search compiled pages
  • read generated markdown directly
  • inspect manifests and graph state
  • ask questions against the vault
  • ingest new material
  • trigger compile and lint runs

Tool Surface

SwarmVault currently exposes these tools:

  • workspace_info
  • search_pages
  • read_page
  • list_sources
  • query_vault
  • ingest_input
  • compile_vault
  • lint_vault

Resource Surface

SwarmVault also exposes read-oriented resources:

  • swarmvault://config
  • swarmvault://graph
  • swarmvault://manifests
  • swarmvault://pages/{path}

Client Setup Pattern

The basic pattern is simple:

  1. Open a terminal in the vault root
  2. Configure your MCP-aware client to launch swarmvault mcp
  3. Let the client call tools and read resources against that workspace

Because the server uses the current working directory as the vault root, you do not need a separate MCP config block inside swarmvault.config.json for the current release.