io.github.Buoy-gg/mcp
io.github.Buoy-gg/mcp · 692 stars
MCP server Let AI agents read and drive a running React Native or Flutter app through Buoy's devtools.
Install
The repo has no one-line install. Follow its README.
Published as
- npm
@buoy-gg/mcpstdio
From the server's entry in the official MCP Registry.
Files
Developer tools that live inside your app.
buoy.gg · Docs · Quick start · Desktop · Pricing
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. 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 · 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. Both 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.
Facts
- Kind
- MCP server
- Repo
- Buoy-gg/buoy
- Group
- Uncategorized
- Stars
- 692
- Last push
- 2026-10-09
- Forks
- 5
- MCP Registry
- io.github.Buoy-gg/mcp
- Homepage
- buoy.gg
- Topics
- devtools, expo, react-native, mcp, android, debugging, developer-tools, ios, react
- 1REAio.github.morluto/reaReverse engineer anything from your terminal or agent with one CLI and MCP server.125.3k
- 2com.browser-use/browser-usecom.browser-use/browser-useControl a real Chrome browser to complete any task: fill forms, extract data, book flights.117.7k
- 3World Monitorapp.worldmonitor/mcpLive markets, conflicts, country risk, chokepoints, energy, and China decision signals. 93 tools.88.3k
- 4Scrapling MCP Serverd4vinci/scrapling🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scraplingdev86.9k
- 5Everythingmodelcontextprotocol/serversThis MCP server attempts to exercise all the features of the MCP protocol. It is not intended to be a useful server, but rather a test server for builders of MCP clients. It implements prompts, tools, resources, sampling, and more to showcase MCP capabilities.85.8k
- 6Fetchmodelcontextprotocol/serversA Model Context Protocol server that provides web content fetching capabilities. This server enables LLMs to retrieve and process content from web pages, converting HTML to markdown for easier consumption.85.8k




