← ClaudeAtlas

bifrost-mcp-setuplisted

Manually wire a Bifrost MCP server into Claude Code (mcp.json) when the automated installer can't run, or add the Bifrost plugin on Claude Desktop and claude.ai through the Plugins UI. Triggers on 'manually add bifrost mcp', 'edit mcp.json for bifrost', 'installer failed', 'add x-bf-vk header', 'manual bifrost setup', 'mcp.json bifrost', 'bifrost in claude desktop', 'claude_desktop_config'.
neXenio/bifrost-plugin · ★ 2 · AI & Automation · score 73
Install: claude install-skill neXenio/bifrost-plugin
# Manual Bifrost MCP Setup Use this when the automated installer (`node bin/install.js` / `/bifrost-setup`) can't run (no internet, policy restriction, etc.). Note: if the plugin itself is installed and enabled, none of this is needed — the plugin's shipped `.mcp.json` registers the `bifrost` server automatically. This skill is for wiring the MCP server WITHOUT the plugin. ## Step 1 — Set your gateway URL and virtual key ```bash # Add to ~/.zshrc or ~/.bashrc (replace with your real values): export BIFROST_URL=https://<your-gateway-host>/mcp export BIFROST_VK=vk_<your-key> source ~/.zshrc # or ~/.bashrc ``` Never commit the VK. It belongs in your shell env only. ## Step 2 — Register the server with the Claude Code CLI ```bash claude mcp add --scope user --transport http bifrost \ "${BIFROST_URL}" --header 'x-bf-vk: ${BIFROST_VK}' ``` The single-quoted `${BIFROST_VK}` is stored as a runtime template — Claude Code resolves it from your shell env on every launch, so the key itself is never written to disk. Re-running the command replaces the same entry (idempotent). ## Step 3 — Restart Claude Code MCP registration changes take effect only after a CC restart. ## Step 4 — Verify ```bash # Confirm the entry is present: claude mcp get bifrost # Confirm env vars are set: echo "URL: ${BIFROST_URL:-NOT SET}" echo "VK: ${BIFROST_VK:+set (${#BIFROST_VK} chars)}${BIFROST_VK:-NOT SET}" ``` If your gateway exposes a skill server, then inside Claude Code call `mcp__bifrost_