Docs›Developers›MCP Server

MCP Server

OmegaVault ships an MCP server — the same one the hosted service uses. Run it yourself and any MCP-capable client can connect to your self-hosted vault.

Quickstart

The server is a single binary. Download or build it, then point it at your data dir:

# Run on the default port (8787)
omegavault-mcp --data ./vault \
               --host 0.0.0.0 \
               --port 8787

Connecting a client

From a client's perspective, your self-hosted server looks identical to the hosted one. Point it at http://your-host:8787/mcp with an access token you mint locally.

See MCP integrations for the per-client config.

Security

  • Always run the MCP server behind TLS (reverse proxy with a cert).
  • Bind to 127.0.0.1 for local-only access; 0.0.0.0 for network access with auth.
  • Mint short-lived tokens; rotate periodically.
  • The server never phones home — your vault stays on your infra.

Resources & tools exposed

The server announces the standard OmegaVault MCP surface:

  • Resources: memories://*, collections://*.
  • Tools: search, create_memory, update_memory, delete_memory.
OmegaVault

Your memory is yours.

Capture once, carry everywhere.

Start Capturing
Free · 200 memories · No card required