AI & MemoryMCP RegistryremoteB · 63

VaultCrux Memory Core MCP server

Name: VaultCrux Memory Core
Author: CueCrux

io.github.CueCrux · Updated 7mo ago

VaultCrux Memory Core — 32 tools: knowledge, decisions, constraints, signals, coverage

At a glance

VaultCrux Memory Core is an MCP server in the AI & Memory category. It is hosted remotely and connects over HTTP, and needs x-api-key and x-tenant-id. It scores B (63/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install VaultCrux Memory Core in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install VaultCrux Memory Core in Claude CodeAnthropic's agentic CLI

Add the server

bash

claude mcp add --transport http vaultcrux-memory-core https://api.vaultcrux.com/memory-core/mcp --header 'x-api-key: <X-API-KEY>' --header 'x-tenant-id: <X-TENANT-ID>'

Fill in your credentials
Replace <X-API-KEY>, <X-TENANT-ID> with your real values. Keep secrets out of any config file you commit.
3
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.

How to install VaultCrux Memory Core in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

{
  "mcpServers": {
    "vaultcrux-memory-core": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.vaultcrux.com/memory-core/mcp",
        "--header",
        "x-api-key:${X_API_KEY}",
        "--header",
        "x-tenant-id:${X_TENANT_ID}"
      ],
      "env": {
        "X_API_KEY": "<X-API-KEY>",
        "X_TENANT_ID": "<X-TENANT-ID>"
      }
    }
  }
}

Fill in your credentials
Replace <X-API-KEY>, <X-TENANT-ID> with your real values. Keep secrets out of any config file you commit.
Why the wrapper?
This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install VaultCrux Memory Core in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

{
  "mcpServers": {
    "vaultcrux-memory-core": {
      "url": "https://api.vaultcrux.com/memory-core/mcp",
      "headers": {
        "x-api-key": "<X-API-KEY>",
        "x-tenant-id": "<X-TENANT-ID>"
      }
    }
  }
}

Fill in your credentials
Replace <X-API-KEY>, <X-TENANT-ID> with your real values. Keep secrets out of any config file you commit.
Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install VaultCrux Memory Core in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.vaultcrux-memory-core]
command = "npx"
args = ["-y", "mcp-remote", "https://api.vaultcrux.com/memory-core/mcp", "--header", "x-api-key:${X_API_KEY}", "--header", "x-tenant-id:${X_TENANT_ID}"]
env = { X_API_KEY = "<X-API-KEY>", X_TENANT_ID = "<X-TENANT-ID>" }

Fill in your credentials
Replace <X-API-KEY>, <X-TENANT-ID> with your real values. Keep secrets out of any config file you commit.
Why the wrapper?
Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install VaultCrux Memory Core in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

{
  "mcpServers": {
    "vaultcrux-memory-core": {
      "serverUrl": "https://api.vaultcrux.com/memory-core/mcp",
      "headers": {
        "x-api-key": "<X-API-KEY>",
        "x-tenant-id": "<X-TENANT-ID>"
      }
    }
  }
}

Fill in your credentials
Replace <X-API-KEY>, <X-TENANT-ID> with your real values. Keep secrets out of any config file you commit.
Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install VaultCrux Memory Core in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

{
  "mcpServers": {
    "vaultcrux-memory-core": {
      "type": "streamableHttp",
      "url": "https://api.vaultcrux.com/memory-core/mcp",
      "headers": {
        "x-api-key": "<X-API-KEY>",
        "x-tenant-id": "<X-TENANT-ID>"
      }
    }
  }
}

Fill in your credentials
Replace <X-API-KEY>, <X-TENANT-ID> with your real values. Keep secrets out of any config file you commit.

How to install VaultCrux Memory Core in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

{
  "servers": {
    "vaultcrux-memory-core": {
      "type": "http",
      "url": "https://api.vaultcrux.com/memory-core/mcp",
      "headers": {
        "x-api-key": "<X-API-KEY>",
        "x-tenant-id": "<X-TENANT-ID>"
      }
    }
  }
}

Fill in your credentials
Replace <X-API-KEY>, <X-TENANT-ID> with your real values. Keep secrets out of any config file you commit.
Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What does VaultCrux Memory Core need from you?

API key — VaultCrux API key used to authorize Memory Core reads

x-api-keyrequiredsecretHTTP header
VaultCrux API key used to authorize Memory Core reads
x-tenant-idrequiredHTTP header
VaultCrux tenant id used to scope Memory Core reads
x-agent-idoptionalHTTP header
Optional agent id override for query and claim-check context

What tools does VaultCrux Memory Core expose?

The server did not respond when we asked for its tool list. It may be offline, or it may not speak HTTP transport.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Third-party hosted service — Your requests and any data in them are sent to api.vaultcrux.com.
No local execution — Nothing is installed or run on your machine.

Client compatibility

Claude Code: NativeClaude Desktop: Via mcp-remoteCursor: NativeCodex CLI: Via mcp-remoteWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 63

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%not measurable
No commit history available.
Adoption20%not measurable
No usage data available.
Transparency20%25%
1/4: ✓ public source repo, ✗ declared license, ✗ documentation, ✗ discoverable tool list.
Provenance15%75%
Links to its own repository; package linkage unverified.
Packaging15%100%
Remote endpoint with documented authentication.

Alternatives to VaultCrux Memory Core

Maintain VaultCrux Memory Core? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![VaultCrux Memory Core on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-cuecrux-vaultcrux-memory-core)](https://mcp-skills-hub.vercel.app/mcps/io-github-cuecrux-vaultcrux-memory-core)

Catalog data refreshed Oct 28, 2026. Something wrong? Report it.