MCP server

Vupt ships a local Model Context Protocol server (vupt-mcp-server). It exposes a set of Vupt-specific tools that any MCP-aware agent can call to query the local store, search past decisions via embeddings, and read journals from sibling Tasks in the same Squad.

Transport

The local server uses MCP stdio transport — the agent CLI spawns the server process directly. There is no HTTP listener and nothing exposed on the network.

The Cloud MCP (Plan 03-07 wave) uses SSE with bearer-token auth and is a Team-tier feature.

Tools available (v1.0)

Tool	Purpose
vupt.search_decisions	RAG over logged decisions via sqlite-vss embeddings
vupt.read_journal	Stream a Task journal as text
vupt.list_squads	List active and recent Squads
vupt.read_file	Read a file from the current Task's worktree
vupt.run_command	Run a shell command in the worktree

Configuration

The server reads ~/.vupt/mcp.toml:

[server]
log_level = "info"

[embeddings]
model = "nomic-embed-text-v1.5"
dim = 768

Sharing context across Tasks (Pro+)

Within a single Squad, sibling Tasks can read each other's journals via vupt.read_journal. This makes coordination patterns possible — a Task can wait for a sibling to write a contract before it depends on it.

Across Squads, decisions logged via vupt.log_decision are searchable by future Tasks via vupt.search_decisions. The embeddings store grows incrementally; indexing is automatic.

Security

The local MCP server only accepts connections on the spawned stdio pipe. No network listener is opened. The server has read-only access to the SQLite store except for the decisions table (where it appends).