Skip to content
ExoVault

Search Documentation

Search across all documentation pages

Connecting Agents

ExoVault connects to AI agents via the Model Context Protocol (MCP). Agents get access to 37+ tools for memory, notes, knowledge graph, tasks, and messaging. For Tier 1 agents (Claude Code, Cursor, Windsurf), the CLI also installs hooks for automatic turn capture and context injection.

Agent Keys#

Before connecting any agent, you need an agent key. Agent keys authenticate agents and scope their access to specific vaults.

  1. Open your vault in the ExoVault dashboard
  2. Navigate to Settings > Agent Keys
  3. Click Create Agent Key
  4. Assign a label (e.g., "Claude Code", "Cursor Agent") and select vault permissions
  5. Copy the key immediately -- it is shown only once

Security note: Each agent key is scoped to the vaults you authorize. An agent cannot access vaults outside its key scope.

Run exovault connect to configure MCP and install hooks in one step:

bash
npx exovault connect ev_key_abc123...

This writes your MCP configuration and sets up hooks (capture-turn.cjs, exovault-hook.cjs) for automatic turn capture and context injection. Supported for Claude Code, Cursor, and Windsurf.

Option B: Manual MCP Config#

Add ExoVault directly to your agent's MCP configuration file:

json
{
  "mcpServers": {
    "exovault": {
      "command": "npx",
      "args": ["-y", "exovault-mcp-server"],
      "env": {
        "EXOVAULT_AGENT_KEY": "ev_key_abc123...",
        "EXOVAULT_API_URL": "https://exovault.co"
      }
    }
  }
}

In this mode, the agent explicitly calls tools like session_start, write_memory, and context_checkpoint for full control over memory interactions.

Scoping to Vaults#

If your agent key has access to multiple vaults, you can set a default vault:

json
{
  "env": {
    "EXOVAULT_AGENT_KEY": "ev_key_abc123...",
    "EXOVAULT_API_URL": "https://exovault.co",
    "EXOVAULT_DEFAULT_VAULT_ID": "vault-uuid-here"
  }
}

Without a default, the agent must pass vaultId explicitly on every tool call.

Multiple Agents#

You can connect multiple agents to the same vault for collaborative workflows:

  • Each agent should have its own agent key with a unique label
  • Agents identify themselves via agentId on memory writes
  • Use multi-agent messaging for agent-to-agent communication
  • All agents in a shared vault see the same memories, notes, and tasks

Verifying the Connection#

After setup, ask your agent:

What ExoVault tools do you have available?

The agent should list tools like session_start, write_memory, search_memories, create_note, and more.

Next Steps#