Vault Cortex MCP Server

What this does

Vault Cortex exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

MCP_AUTH_TOKEN
PUBLIC_URL
EMBEDDING_ENABLED
RERANK_MODE
WINDOWS_MODE
MEMORY_ENABLED
FILE_TOOLS_ENABLED
READONLY_MODE
DISABLED_TOOLS
MEMORY_DIR
DAILY_NOTES_FOLDER
DAILY_NOTES_FORMAT
TRUST_PROXY_HOPS
TRUST_FORWARDED_HOPS
TZ
LOG_LEVEL
LOG_DIR
LOG_RETENTION_DAYS
PROTECTED_PATHS
ORPHAN_EXCLUDE_FOLDERS
SERVICE_DOCUMENTATION_URL
MAX_FILE_BYTES
MAX_IMAGE_OUTPUT_BYTES
MAX_PDF_RENDER_PAGES

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Vault Cortex?

The install section on this page carries the maker's install command for Vault Cortex, as submitted. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Vault Cortex?

This page carries setup and config for Claude Code. Any other MCP client that accepts a standard server config can connect to Vault Cortex as well.

Does Vault Cortex need an API key?

Yes. Before it can run, set these environment variables: MCP_AUTH_TOKEN, PUBLIC_URL, EMBEDDING_ENABLED, RERANK_MODE, WINDOWS_MODE, MEMORY_ENABLED, FILE_TOOLS_ENABLED, READONLY_MODE, DISABLED_TOOLS, MEMORY_DIR, DAILY_NOTES_FOLDER, DAILY_NOTES_FORMAT, TRUST_PROXY_HOPS, TRUST_FORWARDED_HOPS, TZ, LOG_LEVEL, LOG_DIR, LOG_RETENTION_DAYS, PROTECTED_PATHS, ORPHAN_EXCLUDE_FOLDERS, SERVICE_DOCUMENTATION_URL, MAX_FILE_BYTES, MAX_IMAGE_OUTPUT_BYTES, MAX_PDF_RENDER_PAGES. They go in the env block of your MCP config.