Governed MCP memory server
Wire Heartwood into any MCP client for governed writes and agent-facing memory tools — remember, recall, explain_recall, forget, egress, and faithfulness checks.
Configure
Add Heartwood to your MCP client config. Override HEARTWOOD_DB_PATH to share the same store built by import-markdown or the warm recall service.
{
"mcpServers": {
"heartwood-memory": {
"command": "python",
"args": ["-m", "heartwood.adapters.mcp_server"],
"env": {
"HEARTWOOD_DB_PATH": ".heartwood/heartwood.db",
"HEARTWOOD_TENANT": "tenant:ops"
}
}
}
}Tools
• remember — tenant-aware governed write (classification, roles, attrs, source IDs, provenance signing, audit, encryption, indexing) • recall — policy-enforced recall; denied memories are never returned or counted • explain_recall — ranking/freshness explanation with no denied-candidate side channels • forget — crypto-shred the subject key and purge derived memories • evaluate_egress — check source spans before external-model egress • assess_faithfulness — check generated-memory claims against source spans • memory — Anthropic memory-tool-compatible /memories surface • health — readiness, warmed tenants, model names, key-custody mode
Keep it local for now
Keep Heartwood embedded and local. Do not expose the MCP server over a remote transport until the deployment has explicit auth, network isolation, and key custody configured.
Adapted from docs/integrations/mcp-quickstart.md in the open-source core.