Vibedock sits in your menu bar and lets you toggle Claude Code MCP servers on and off — instantly, without touching a config file.
If any of this sounds familiar, Vibedock is for you.
Adding, removing, or disabling an MCP server means opening claude_desktop_config.json, finding the right braces, and hoping you didn't break the syntax. Vibedock does it in one click.
Every config change needs a full session restart. Vibedock kills and relaunches Claude automatically — so you toggle a server and keep working.
Every active MCP server adds tools to your context window — even the ones you rarely need. Disable what you're not using and stop burning tokens on idle servers.
Enable or disable any MCP server in one click. Changes take effect immediately.
Vibedock automatically kills and restarts your Claude sessions after a toggle. Zero friction.
Sees your global MCPs and per-project configs. Organized by project, always up to date.
Watches your config files. When something changes, Vibedock updates instantly.
Works with Terminal, iTerm2, VS Code and Warp. Sessions relaunch in the right window.
Every unused MCP bloats your context window. Disable what you don't need and save thousands of tokens per message.
One-time purchase. Yours forever.
Vibedock License
1 Mac · one-time purchase
MCP (Model Context Protocol) servers extend Claude Code with tools — file access, web search, databases, APIs, and more. Vibedock lets you manage which ones are active without editing JSON files.
Yes. Vibedock reads your Claude Desktop config file and shows those MCP servers alongside your Claude Code ones.
macOS 13 Ventura or later.
Yes. Deactivate from Preferences on your old Mac, then activate on the new one with the same license key.
No. Vibedock is a one-time purchase. Pay once, use forever.