About Buoy-gg
Buoy-gg provides in-app developer tools for inspecting and changing a running React Native or Flutter app, including network activity, storage, routes, and rendering. Its MCP server lets AI editors interact with the running app, while Buoy Desktop can show connected tools across devices.
Key features
- 01Inspect and modify app state while it runs
- 02Tools for network, storage, routes, and rendering
- 03Connect app tools to Buoy Desktop
- 04MCP access for AI editors
- 05Sim Farm and Chrome Farm support
Use cases
- 01Inspect requests and override network responses
- 02Change cached data or force loading and error states
- 03Let an AI editor read and modify a running app
MCP support
The MCP server lets AI editors read and change a running app, and also runs the Sim Farm and Chrome Farm. App tool access requires `@buoy-gg/external-sync` in the app; MCP availability varies by account plan.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
60Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| deviceId | string | No | Target device id (auto-selected if one is connected). |
Details
From the project README
Buoy puts a floating menu in your app. Use it to check web calls, storage and query caches. You can check stores, routes, renders and speed too. Change them while your app runs. Link the same session to Buoy Desktop or MCP. Or use Ask Buoy right in your app.
Flutter has its own setup for debug builds. Capacitor / Ionic (Beta) uses the web tools on iOS and Android. Solid (Beta) works in Solid 1.9 apps built with Vite. Vue and Nuxt (Beta) works in Vue 3.3 and up built with Vite, and in Nuxt 4. Three.js (Beta) works with R3F and plain apps. Use Scene to see and edit 3D objects.
Get started
The quickest way in is to let your coding agent do it. Paste the prompt below into Claude Code, Cursor or Codex. It follows buoy.gg/install.md, installs the core plus the tools that match your dependencies, and tells you how to check it on the device.
Agent install prompt
Install Buoy, the in-app devtools for React Native and Expo, in this project.
Read the full instructions first:
curl -fsSL https://buoy.gg/install.md
Read the raw text, not a summary. If curl is unavailable, use any HTTP tool you have. Ask me to paste the document only if nothing can fetch it.
Do the install yourself: inspect the repo, run the commands, edit the files. Do not hand me steps you can run.
Work out the routine decisions from the repo: package manager, which app to target, where the menu mounts, which Buoy tools match the dependencies already installed. If Buoy is already partly installed, repair and extend it; never add a second mount, provider, or package set.
When instructions conflict, follow this order: what I say here, then the document's rules about which packages exist and what needs my permission, then this project's own constraints, then the rest of the document, then your judgment.
Ask me before: adding a native dependency, opening a browser or creating an account, changing what a production build does beyond what the document specifies, or anything hard to undo. Do not commit.
You are not done when the packages install. Run this project's existing typecheck; add no tooling. Then report what you installed and why, what you skipped and why, every file you changed, what you verified, and the exact steps I take on the device to confirm the menu appears and captures a request.
To install by hand, start with the core and the Network tool, then sign in:
npm install @buoy-gg/core @buoy-gg/network
npx --package=@buoy-gg/core buoy login
Mounting the menu, loading your key and adding more tools are covered in the Quick start. You need a development build and a Free or Pro Buoy account.
See it work
Each tool has a short film on its docs page, recorded on a real app.
 |  |  |
| Read, time and override requests | Edit cached data, force loading and error states | An agent inside your app |
Tools
Install only the ones your app needs. Each link goes to its guide.
Network · Storage · Time Machine · Scenarios · Clock · Lifecycle · Location · Permissions · Ask Buoy · Env · React Query · Routes · Debug Borders · Highlight Updates · Bench · JS Top · Images · Scene (Beta) · Assets · Events · Console · Sentry · Redux · Zustand · Jotai · Impersonate · TV Remote · Focus Inspector · Camera · Overlay
Beyond the device
Buoy Desktop shows your connected tools in desktop panels and lets you switch between devices. The MCP server lets an AI editor read and change the running app. A free account gets the basic MCP, and Pro adds the full MCP. The MCP also runs the Sim Farm. It gives Buoy Optimize many slim iOS sims or Android phones, so your agent can try many speed ideas at once. The Chrome Farm runs many slim Chromes on your web app, so your tests run side by side. Buoy Web lets your AI use Chrome for you, with real clicks. It needs nothing in your app. Desktop and the MCP's app tools need @buoy-gg/external-sync in your app; the Desktop guide covers the connection.
Buoy starts in development builds. Turning it on in a shipped app takes Pro and your own access checks; read the component reference before you do.
Feedback
Found a bug, or want a tool that doesn't exist yet? Open an issue. Feature requests shape what gets built next.
License
Proprietary software. © Buoy LLC. All rights reserved. See the Terms of Service.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.