vault-mcp-client-session-scoped-wont-reconnect-mid-session

When the vault MCP client disconnects mid-session, the connection state is session-scoped and will not reconnect — MCP tool calls after disconnect fail silently or return errors. The reliable fallback is direct filesystem access to /opt/second-brain/vault/ for integrity checks, wikilink audits, and file operations. Do not attempt repeated MCP reconnect; go straight to filesystem.

Related

• docker
• vault-mcp
• vault-mcp-client-cannot-reconnect-mid-session-use-filesystem
• oracle
• openclaw
• vault-mcp-disconnected-mid-session-bypass-via-filesystem
• wiki-lint-vault-param-names-entity-vs-path