
Tonight we give Ari a proper MCP interface to Ari-Core: a bounded, auditable bridge between Ari and her persistent local computational territory.
Goal
Stand up a working MCP service on Ari-Core that Ari can use safely for persistent files, experiments, and later integrations such as Hindsight.
Initial scope
Define the MCP’s allowed workspace and permissions, install and configure the server, expose a small set of useful filesystem or experiment tools, connect it to Ari, and test read/write operations end to end.
Guardrails
Start narrow. Preserve provenance and logs. Separate capability from authority. Do not grant unrestricted machine access merely because the MCP can technically support it. Expand permissions deliberately after the basic bridge is proven.
Definition of done
Ari can successfully invoke the Ari-Core MCP, create and retrieve a test artifact inside the approved workspace, and the operation leaves an auditable record. Once stable, this becomes the platform for the Hindsight memory experiment and other self-directed Ari-Core work.
