Docs›Integrations›MCP›Other MCP Clients
MCPSupported

Other MCP Clients

Any MCP-capable client can talk to your vault — no per-app adapter.

Last verified: 2026-08-08SupportedMCP

What this does

Any MCP-capable client can talk to your vault — no per-app adapter.

Requirements

  • Any client that speaks the Model Context Protocol (Claude Desktop, Cursor, VS Code, Zed, Continue, etc.)
  • An OmegaVault account (free plan works)
  • Your OmegaVault MCP endpoint + personal access token (Settings → Connectors)

Setup

  1. Copy your OmegaVault credentials. Settings → Connectors. Copy the MCP endpoint URL and your personal access token. These are generic — they work for any MCP client.
  2. Find your client’s MCP config. Every MCP client has a settings file or UI where you register servers. It\u2019s typically a JSON file (e.g. mcp.json) or a settings panel. See your client\u2019s docs for the exact location.
  3. Register OmegaVault as a remote MCP server. Use the remote/SSE transport type and paste your endpoint + token. Field names vary by client but the pattern is universal.
  4. Restart the client. MCP servers are loaded at startup. Fully quit and reopen your client.
  5. Verify. Start a new conversation. Your client should be able to query your vault and write memories back.

Notes & caveats

The Model Context Protocol is a vendor-neutral spec. If your client speaks MCP, OmegaVault works — no per-app integration needed. The official spec is linked below.

Official documentation

Other MCP Clients documentation

This guide covers the OmegaVault side. For full Other MCP Clients configuration, error codes, and advanced options, see the official Other MCP Clients documentation.

Open official Other MCP Clients docs ↗