Troubleshooting

The most common cause: your AI tool wasn't restarted after the config was written.

• Claude Desktop: Quit fully (Cmd-Q on Mac, not just close the window). Then relaunch.
• Cursor: Restart Cursor. Reload-window from the command palette is sometimes not enough — full quit and relaunch.
• VS Code: The MCP config is per-project, in .vscode/mcp.json. Make sure you're in the right project, then reload the window.

If your tool was already running when the install script ran, it doesn't pick up the new config until restart.

Still not seeing tools? Check that the config file actually has SubVault in it. Locations:

• Cursor: ~/.cursor/mcp.json
• Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
• Claude Desktop (Linux): ~/.config/Claude/claude_desktop_config.json
• VS Code: .vscode/mcp.json in your project

You should see a subvault entry under mcpServers (or servers for VS Code).

This means your API key was rejected. Three causes, in order of likelihood:

1. The key was regenerated. If you (or someone with access to your dashboard) clicked Regenerate, the old key was invalidated immediately. Anywhere you'd installed it needs the new key.
2. The key has whitespace or got truncated. Re-copy it from your dashboard using the Copy button. Manual selection sometimes grabs an extra space or misses the last character.
3. The key isn't in the config the way the tool expects. The header line should be "Authorization": "Bearer sv_live_..." — the word Bearer with a space, then the key.

To verify the key independently, paste this in a terminal (replace with your real key):

curl -X POST https://mcp.subvault.ai/mcp \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

If that returns a list of tools, the key works and the issue is in your tool's config. If it returns 401, the key itself is the problem — regenerate it from your dashboard.

The signup page shows the key once, on purpose. If you didn't save it:

1. Sign in at the dashboard with your email and password.
2. If you still have access via any tool that's already configured, the dashboard's Regenerate button mints a new key and invalidates the old one.
3. If you have no way to access the API, email info@subvault.ai from the address you signed up with. We'll regenerate the key for you.

SubVault tools are present but your AI isn't calling them. A few causes:

• Your vault might be empty. If you just signed up and haven't vaulted anything, remember has nothing to return. Try first: "Remember that I work in Python." Then in a new chat: "What language do I work in?"
• The phrasing didn't trigger your AI. Direct asks work best: "vault this conversation", "remember what we just discussed", "what do I know about X?"
• Tools toggled off. In Claude Desktop, click the tool icon in the chat input to verify SubVault tools are enabled. In Cursor, the MCP icon at the bottom shows connected servers.

The script looks for the config directories of Claude Desktop, Cursor, and VS Code. If none are found, it prints that message.

• Make sure the tool is actually installed and has been opened at least once. The config directory is created on first launch.
• If you're using a tool the script doesn't auto-detect (e.g. Zed, Continue, custom MCP clients), use the Manual JSON tab in setup docs.

Email info@subvault.ai from the address you signed up with, subject "Delete my account."

We'll delete your user record, your API keys, and your entire vault — usually within one business day. We'll confirm when it's done.

This deletes everything: facts, decisions, action items, your account row, all API keys. There's no undo.

Typical recall is under 500ms. If it feels slow:

• The first call after a long idle period can take a few seconds — the server warms up. Subsequent calls are fast.
• Very large vaults (10K+ items) take slightly longer to assemble. This is normal.
• Network latency adds tens to a hundred milliseconds depending on where you're connecting from.

If you see consistent multi-second responses on small vaults, that's a real bug — please email info@subvault.ai with your workspace ID (visible on your dashboard).

Email info@subvault.ai with whatever info you have. The workspace ID from your dashboard helps us find your account quickly. Screenshots of error messages are gold.

For security issues, see our security policy.