Set up MCPBytes Vault.

After installation, register for all projects with the command for your OS. Launch Claude with MCPBYTES_API_KEY available in its environment, then use /mcp to check the connection. Custom install path? Use the command printed by the installer. Claude Code docs

claude mcp add --transport stdio --scope user mcpbytes-vault -- "$HOME/Library/Application Support/MCPBytes/Vault/bin/mcpbytes-vault"

Merge this table into ~/.codex/config.toml. Replace YOUR_USER, or use the paths printed by the installer. env_vars forwards the API key from Codex’s environment without storing its value here. The installer also prints a codex mcp add command; after using it, add env_vars to the resulting table. Restart or reconnect the client afterward. Codex docs

[mcp_servers.mcpbytes-vault]
command = "/Users/YOUR_USER/Library/Application Support/MCPBytes/Vault/bin/mcpbytes-vault"
args = []
env_vars = ["MCPBYTES_API_KEY"]

Merge into ~/.cursor/mcp.json or .cursor/mcp.json. Replace YOUR_USER and start Cursor with MCPBYTES_API_KEY available in its environment. Cursor docs

{
  "mcpServers": {
    "mcpbytes-vault": {
      "command": "/Users/YOUR_USER/Library/Application Support/MCPBytes/Vault/bin/mcpbytes-vault",
      "args": [],
      "env": {
        "MCPBYTES_API_KEY": "${env:MCPBYTES_API_KEY}"
      }
    }
  }
}

Merge into .vscode/mcp.json, or open MCP: Open User Configuration. Replace YOUR_USER. VS Code prompts privately for the API key; the value is not part of this sample. VS Code docs

{
  "inputs": [
    {
      "type": "promptString",
      "id": "mcpbytes-api-key",
      "description": "MCPBytes API key",
      "password": true
    }
  ],
  "servers": {
    "mcpbytes-vault": {
      "type": "stdio",
      "command": "/Users/YOUR_USER/Library/Application Support/MCPBytes/Vault/bin/mcpbytes-vault",
      "args": [],
      "env": {
        "MCPBYTES_API_KEY": "${input:mcpbytes-api-key}"
      }
    }
  }
}

Merge into ~/.gemini/settings.json. Replace YOUR_USER. The explicit env mapping forwards MCPBYTES_API_KEY from Gemini’s environment; sensitive variables may otherwise be filtered. Gemini CLI docs

{
  "mcpServers": {
    "mcpbytes-vault": {
      "command": "/Users/YOUR_USER/Library/Application Support/MCPBytes/Vault/bin/mcpbytes-vault",
      "args": [],
      "env": {
        "MCPBYTES_API_KEY": "${MCPBYTES_API_KEY}"
      }
    }
  }
}

Merge into opencode.json or ~/.config/opencode/opencode.json. Replace YOUR_USER and make MCPBYTES_API_KEY available to OpenCode. OpenCode docs

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mcpbytes-vault": {
      "type": "local",
      "command": [
        "/Users/YOUR_USER/Library/Application Support/MCPBytes/Vault/bin/mcpbytes-vault"
      ],
      "enabled": true,
      "environment": {
        "MCPBYTES_API_KEY": "{env:MCPBYTES_API_KEY}"
      }
    }
  }
}

Merge into .omp/mcp.json or your active OMP profile’s mcp.json. Replace YOUR_USER and launch OMP with MCPBYTES_API_KEY available. The env value names the variable to copy from the parent environment. oh-my-pi docs

{
  "mcpServers": {
    "mcpbytes-vault": {
      "command": "/Users/YOUR_USER/Library/Application Support/MCPBytes/Vault/bin/mcpbytes-vault",
      "args": [],
      "env": {
        "MCPBYTES_API_KEY": "MCPBYTES_API_KEY"
      }
    }
  }
}

Install the third-party pi-mcp-adapter, restart Pi, and merge the JSON into ~/.config/mcp/mcp.json or project .mcp.json. Replace YOUR_USER and supply MCPBYTES_API_KEY in Pi’s environment. The MCPBytes REST skill alone does not connect the local Vault. Pi docs

pi install npm:pi-mcp-adapter

Merge into ~/.codeium/windsurf/mcp_config.json. Replace YOUR_USER and make MCPBYTES_API_KEY available to Windsurf. Windsurf docs

{
  "mcpServers": {
    "mcpbytes-vault": {
      "command": "/Users/YOUR_USER/Library/Application Support/MCPBytes/Vault/bin/mcpbytes-vault",
      "args": [],
      "env": {
        "MCPBYTES_API_KEY": "${env:MCPBYTES_API_KEY}"
      }
    }
  }
}

Run goose configure → Add Extension → Command-Line Extension. Use mcpbytes-vault as the name and the executable command/arguments printed by the installer. Add MCPBYTES_API_KEY through the local environment-variable prompt. In the desktop app, add a Standard IO extension with the same settings. Goose docs

goose configure

Merge into settings.json, replacing YOUR_USER. Supply MCPBYTES_API_KEY privately in this server’s env settings, then check Settings → AI → MCP Servers for its status. Keep the key value out of shared settings and chat. Zed docs

{
  "context_servers": {
    "mcpbytes-vault": {
      "command": "/Users/YOUR_USER/Library/Application Support/MCPBytes/Vault/bin/mcpbytes-vault",
      "args": [],
      "env": {}
    }
  }
}

Choose a local/stdio server. Copy command and args from the installer’s mcp-server.json into your client’s matching settings, and supply MCPBYTES_API_KEY through its private environment settings. Replace YOUR_USER in these examples. Client-specific wrappers may differ. A remote-only connector cannot launch this local executable. For DeepSeek models, follow the instructions for the agent application that runs them. Other local MCP clients docs

{
  "mcpServers": {
    "mcpbytes-vault": {
      "command": "/Users/YOUR_USER/Library/Application Support/MCPBytes/Vault/bin/mcpbytes-vault",
      "args": []
    }
  }
}