ContextVaultContextVault

Docs

Connect ContextVault to your AI client

Use the hosted MCP endpoint to let supported AI clients search and store shared team memory.

MCP Endpoint

Point MCP-compatible clients at the hosted ContextVault server. The app handles authorization, workspace scoping, and memory access after the user signs in.

Server URL

https://mcp.contextvault.dev
  • The hosted MCP endpoint uses HTTP transport and requires authentication.
  • On first connection, your client should open a browser-based OAuth flow.
  • After sign-in, requests are tied to your ContextVault user and active workspace.
  • Use group-scoped memories when only part of the workspace should see a memory.

Cursor

Add ContextVault as a remote HTTP MCP server. Cursor starts the OAuth sign-in flow the first time it connects.

{
  "mcpServers": {
    "contextvault": {
      "url": "https://mcp.contextvault.dev"
    }
  }
}

Paste this in Cursor Settings → MCP, or save it as `~/.cursor/mcp.json` (global) or `.cursor/mcp.json` (project).

Windsurf

Windsurf Cascade uses a `serverUrl` field for remote HTTP MCP servers. Point it at the `/mcp` path on the hosted endpoint.

{
  "mcpServers": {
    "contextvault": {
      "serverUrl": "https://mcp.contextvault.dev/mcp"
    }
  }
}

Add this from Windsurf Settings → Tools → Add Server, or edit `~/.codeium/mcp_config.json`. Some installs keep the file at `~/.codeium/windsurf/mcp_config.json`.

Claude Code

Add ContextVault to the project MCP configuration so Claude Code can discover the hosted server and start the OAuth sign-in flow.

{
  "mcpServers": {
    "contextvault": {
      "url": "https://mcp.contextvault.dev"
    }
  }
}

Save this in the project `.mcp.json` file. Claude Code should prompt for authorization the first time it connects.

Codex

Codex uses TOML configuration for MCP servers and a streamable HTTP client. Add ContextVault to your Codex config, then run the MCP login flow if your Codex version does not start it automatically.

[features]
experimental_use_rmcp_client = true

[mcp_servers.contextvault]
url = "https://mcp.contextvault.dev"

This entry belongs in `~/.codex/config.toml` or the Codex config location your client uses. Recent Codex builds also support `codex mcp add contextvault --url https://mcp.contextvault.dev`.

Groups

Groups control which teammates can find and reuse each set of memories. They are the main way Team and Enterprise workspaces keep shared context scoped without creating separate accounts.

  • Groups are available on Team and Enterprise plans.
  • Each memory belongs to one group, and members can search memories from the groups they belong to.
  • Use groups for departments, clients, projects, or other boundaries where shared memory should stay scoped.
  • Admins and managers can create, rename, and archive groups from the dashboard.
  • Archiving a group does not delete memories, but the group is removed from active selectors. Move memories first if they should remain active under another group.
  • The dashboard includes a bulk move tool for moving memories from one group to another.

In the dashboard, open Workspace Management, then Groups. From there you can add a group, edit a group name and choose Rename from Actions, archive a group, or use Move memories to transfer records between groups.