MetaVault keeps the key on this machine. The agent asks for a capability, a local model scores it, you approve, and the secret never enters the chat.
Apache-2.0 · No account · No telemetryPolicy denies it before the model is asked. The warden can narrow a scope or force you to look. It cannot widen one, and it never sees the key.
Pick a step. The buttons are a simulation. Nothing is stored, and no key is real.
You type it in the app. The field clears. The agent learns the alias and the ceiling, never the value.
Stored. The field is empty, and it stays empty.
Cursor calls the MCP tool. There is no secret field on the call.
llama3.2:3b on this machine. The prompt is the agent, the alias, the scope, and the reason.
Writes always ask. A standing approval is only for a read the warden called low.
The key is not in this payload.
Apache-2.0. The vault, the warden, the MCP server, and the audit log ship together. There is no tier to upgrade into.
Fork it, read it, run it without an account.
The daemon binds to localhost. The warden defaults to a model you run.
{
"mcpServers": {
"openvault": {
"command": "node",
"args": ["<openvault>/dist/packages/mcp/src/server.js"],
"env": { "OPENVAULT_AGENT_ID": "cursor", "OPENVAULT_IDE": "Cursor" }
}
}
}