Root-cause first
Separate server, database, and client problems in one screen instead of editing configs blindly.
Connections
Connection diagnostics
Check the server, the database, and the client before you start guessing.
Overview
What Connection diagnostics does
Diagnostics answers the first question every broken MCP connection raises: is it the server, the database, or the client? Before you touch any client settings, the tab confirms whether the bundled server script exists and whether your local vault database is reachable. Server readiness is verified at the source, so you never chase a client-side ghost that was really a missing file.
When a read fails, Diagnostics narrows the cause fast. A green server check plus a reachable database means the problem is on the client — often an un-restarted app or an MCP server disabled in that tool's own settings. A red check points you at the exact path to fix, turning a vague "it's not working" into a concrete next step.
DiagnosticsSetup
Why it matters
The payoff for your AI memory
Verified server readiness
Confirm the bundled script exists and the vault database path resolves before restarting anything.
Faster troubleshooting
A passing check tells you to look at the client; a failing one names the file or path at fault.
How it works
From first launch to reusable memory
- 1
Open Connection and switch to the Diagnostics tab.
- 2
Run the check to test the server script and vault database access.
- 3
Read the result to see whether the server, database, or client is the weak link.
- 4
Fix the flagged item, then re-run Install or restart the client and re-check.
FAQ
Common questions
Why can't my AI client read the vault over MCP?
Run Connection → Diagnostics. It checks whether the server script exists and the vault database is reachable; if both pass, the client likely needs a restart or has the MCP server disabled in its own settings.
How do I check if the 1AIVault MCP server is running?
The Diagnostics tab verifies server script availability and vault database access, so you can confirm the server side is healthy before troubleshooting any individual client.
Related
More Connections features
Connect Your AI Tools in One Click
Install the MCP bridge for Claude Desktop, Claude Code, Cursor, Cline, and Codex without hand-editing JSON. The Connection view writes the config, runs a diagnostic, and confirms the link is alive.
Learn moreAutomatic MCP repair
Existing Claude Desktop, Claude Code, Cursor, Cline, Codex, ChatGPT, and OpenCode connections can be refreshed before stale settings break.
Learn moreBroad AI tool support
The current source registry covers 18 AI tools across desktop apps, CLIs, editors, and coding agents.
Learn moreLocal memory, shared everywhere
Give every AI tool the same memory.
Start free, import real conversations, and reuse your memory across every AI agent you already use.