dig + Pi
WIPA pi.dev package pointing at the portable dig skill is in progress. Until it lands, any pi agent drives dig through the `dig mcp` server.
Install — about 10 seconds
Pi
# pi shim is landing — drive dig over MCP meanwhile
{ "mcpServers": { "dig": { "command": "dig", "args": ["mcp"] } } }
The native Pi shim is still landing. Until it does, the MCP server gives Pi the full dig surface today.
Or register the MCP server directly
The universal entry: one stdio server, accepted by any MCP-capable client.
mcp config
{
"mcpServers": {
"dig": {
"args": [
"mcp"
],
"command": "dig"
}
}
}
What Pi gets
dig drives the same surface through every path. Read tools never change state; mutating tools preview first, and a single dig_undo steps any change back.
- dig_find
- ranked search across the knowledge base
- dig_recall
- token-budgeted, provenance-tagged memory recall
- dig_retain
- capture a note, doc, or session into memory
- dig_drift
- report divergence from policy
- dig_log
- read the change history
- dig_export
- export a reproducible dataset
- dig_org
- reorganize to policy (preview unless apply)
- dig_reconcile
- converge to policy (preview unless apply)
- dig_undo
- step back the last change