Vibedock

Product Introduction

1. Definition: Vibedock is a macOS menu bar utility application designed for developers and power users of Anthropic's Claude Code and Claude Desktop AI assistants. It functions as a real-time Model Context Protocol (MCP) server management tool.
2. Core Value Proposition: Vibedock exists to eliminate the token waste and context window bloat caused by inactive MCP servers. It provides instant, one-click toggling of MCP tools directly from the macOS menu bar, automatically restarting Claude sessions to apply changes without manual configuration file edits, thereby optimizing AI interaction costs and performance.

Main Features

1. Instant MCP Toggle: This feature allows users to enable or disable any configured MCP server with a single click from the dropdown menu. How it works: The application parses the user's global and per-project Claude configuration files (typically claude_desktop_config.json), presents a list of available MCP servers organized by project, and provides toggle switches. The underlying technology modifies the active session's environment or instructs the Claude client to reload configurations with the specified servers disabled.
2. Automatic Session Relaunch: After a user toggles an MCP server, Vibedock automatically terminates and restarts the active Claude Code or Claude Desktop session. How it works: The app detects the active terminal process (compatible with Terminal, iTerm2, VS Code Integrated Terminal, and Warp) running a Claude session, sends a kill signal, and re-executes the resume command (e.g., claude --resume [session-id]) to restore the session in the same terminal window with the updated MCP context, ensuring changes take effect with zero manual intervention.
3. Live File System Scanning: Vibedock continuously monitors the user's Claude configuration files for changes. How it works: Using macOS File System Events API, the app watches the directories where claude_desktop_config.json and project-specific .clauderc files are stored. When a file is modified, added, or removed, Vibedock rescans and instantly updates its menu bar interface to reflect the new list of MCP servers, maintaining an always-accurate view without requiring a manual refresh.

Problems Solved

1. Pain Point: Context Window Pollution and Unnecessary Token Consumption. Every active MCP server injects its tool definitions (which can be hundreds of tokens each) into every AI message's context window, regardless of whether the tools are used. This inflates token usage per message, increasing costs and potentially reducing the effective context length for the actual task.
2. Target Audience: The primary user personas are software developers, data engineers, and technical professionals who use Claude Code extensively in their workflow. This includes Full-Stack Developers integrating database MCPs (Postgres, Redis), DevOps Engineers using infrastructure tools, and Researchers employing specialized data-fetching servers, all of whom manage multiple projects with different MCP requirements.
3. Use Cases: A developer switching from a backend project using Postgres and Redis MCPs to a frontend project where those tools are irrelevant can instantly disable them to save tokens. A user experimenting with a new web-search MCP server can quickly disable it if it's performing poorly without editing JSON configs. A team lead can optimize shared Claude session costs by ensuring only relevant tools are active for specific tasks.

Unique Advantages

1. Differentiation: Unlike manual management (editing JSON configuration files) or using shell scripts, Vibedock offers a persistent, system-level GUI control panel. Compared to hypothetical alternative methods, it requires no command-line memorization, automatically handles session state persistence, and provides real-time visual feedback. Its project-aware organization surpasses basic global toggle scripts.
2. Key Innovation: The integration of automatic, intelligent session relaunch is the critical innovation. Simply toggling a setting in a config file does not affect already-running Claude sessions. Vibedock's ability to identify the specific terminal session, kill it, and seamlessly restart it with the exact same state (--resume) is what makes the toggle "instant" and practical, bridging the gap between configuration change and runtime effect.

Frequently Asked Questions (FAQ)

1. Does Vibedock work with both Claude Code and Claude Desktop? Yes, Vibedock is compatible with both Claude Code (the VS Code extension) and the standalone Claude Desktop application. It reads the shared MCP configuration files used by both clients, allowing you to manage servers for all your Claude interfaces from one central menu bar utility.
2. How does Vibedock actually save me money on AI token usage? Vibedock saves costs by reducing the context window size. Each inactive MCP server can add ~700 or more tokens to every single message you send. By disabling unused servers, you shrink the context sent to the AI model per message, directly lowering token consumption and your overall API bill, especially for high-volume users.
3. What happens if I toggle an MCP server while in the middle of a Claude conversation? Vibedock automatically resumes your session. When you toggle a server, it kills your current Claude session and immediately restarts it using the claude --resume [ID] command. This restores your conversation history and context, so you can continue your chat with the updated set of MCP tools active, with minimal disruption.
4. Is Vibedock a subscription service or a one-time purchase? Vibedock is a one-time purchase license, not a subscription. You pay a single fee (e.g., $19.99 for 2 Macs) for a perpetual license that includes free updates, with no recurring charges. A 3-day free trial is available to test all features before buying.