VaultCrux Memory Core — tools: knowledge, decisions, constraints, signals, coverage
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
https://api.vaultcrux.com/memory-core/mcpHeaders: x-api-key, x-tenant-id, x-agent-id
Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-cuecrux-vaultcrux-memory-core": {
"url": "https://api.vaultcrux.com/memory-core/mcp"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Paste an API key, bearer token, or session value from the provider. It is used once to list inventory and discarded after the request.
VaultCrux API key used to authorize Memory Core reads
VaultCrux tenant id used to scope Memory Core reads
Optional agent id override for query and claim-check context
VaultCrux Memory Core is an MCP server for VaultCrux Memory Core — tools: knowledge, decisions, constraints, signals, coverage. It supports HTTP transport.
Use the generated config in Install. It points your client at the advertised remote endpoint shown on this page.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://api.vaultcrux.com/memory-core/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://api.vaultcrux.com/memory-core/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://api.vaultcrux.com/memory-core/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://api.vaultcrux.com/memory-core/mcp.
VaultCrux Memory Core uses HTTP transport. Endpoint: https://api.vaultcrux.com/memory-core/mcp.
VaultCrux Memory Core inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
VaultCrux Memory Core is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.