Buoy

What Buoy-gg/buoy MCP server does

Buoy-gg/buoy MCP server connects an AI editor to a running application instrumented with Buoy. The agent can inspect and modify supported parts of the app while it is running, including network activity, storage, query caches, routes, application state, rendering behavior, and performance information.

The underlying Buoy toolkit places a floating developer menu inside the app. The MCP connection provides an external way for an AI editor to work with the same connected session. This makes the server relevant for debugging development builds, reproducing runtime conditions, and checking behavior that is difficult to understand from repository files alone.

Support described in the repository covers React Native, Expo, and Flutter. Capacitor/Ionic and Three.js integrations are identified as beta, but the README does not specify the complete MCP capability set for those platforms.

How it works

The application first includes Buoy and the tools appropriate to its dependencies. The app then connects to Buoy’s external synchronization layer, allowing the MCP connection and Buoy Desktop to access the running session. An AI editor can subsequently read information from the app and apply supported changes through MCP.

The repository lists separate Buoy tools for areas such as network requests, storage, React Query, routes, Redux, Zustand, Jotai, console output, permissions, lifecycle, location, and performance. The MCP offering is tiered: a Free account includes the basic MCP, while a Pro account includes the full MCP. Both tiers require @buoy-gg/external-sync in the application.

Setup and configuration

Manual installation starts with the Buoy core package and Network tool:

npm install @buoy-gg/core @buoy-gg/network
npx --package=@buoy-gg/core buoy login

After logging in, the application must mount the Buoy menu, load its key, and add any other required tools according to the Quick Start documentation. The README states that a development build is required and that a Free or Pro Buoy account is needed.

For MCP access, add @buoy-gg/external-sync to the app and follow Buoy’s MCP and Desktop connection documentation. The repository does not provide a required environment-variable list or an MCP transport configuration in the supplied material.

Tools and capabilities

The listed Buoy tools include:

• Network inspection, timing, and request overrides
• Storage, environment values, and query-cache editing
• React Query loading and error-state controls
• Routes, lifecycle, permissions, location, and clock controls
• Redux, Zustand, and Jotai inspection
• Console, events, Sentry, assets, and image tools
• Debug borders, update highlighting, performance monitoring, and JavaScript profiling
• Camera, focus inspection, overlays, TV remote controls, and impersonation
• Scene for Three.js applications, marked as beta

The exact subset available through MCP depends on the account tier and the tools installed in the app. Buoy Desktop can also display connected tools in desktop panels and switch between devices, but it is a separate product from the MCP server.

Limitations and notes

Buoy-gg/buoy MCP server is intended for a running, instrumented app rather than static source analysis. The README specifically describes development-build usage. Enabling Buoy in a shipped app requires Pro and application-specific access checks.

The repository describes the software as proprietary and directs users to Buoy’s terms. The supplied material does not document offline operation, supported MCP transports, or a complete list of editor-specific configuration files. Capacitor/Ionic and Three.js support are marked beta, so verify their current MCP behavior before depending on them in production workflows.