GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者による説明(英語の原文)
Run, hot-reload and screenshot Flutter, web, React Native and native iOS/Android apps.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"baton": {
"command": "npx",
"args": [
"-y",
"baton-run"
]
}
}
}ターミナルでこれを実行します
claude mcp add baton -- npx -y baton-runプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"baton": {
"command": "npx",
"args": [
"-y",
"baton-run"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"baton": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"baton-run"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月9日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント kanumuri9593 で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.2.10)がレジストリに届いたのは28 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
同じカテゴリには:GitHub, Desktop Commander, Cloudflare MCP
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
Baton
Run, hot-reload, check and screenshot your apps from any coding agent.
Flutter, Next.js, Vite, React Native / Expo, and native iOS and Android, from a terminal, the Baton app, or any MCP client.
= 24" src="https://img.shields.io/badge/node-%3E%3D24-339933">
Website · Set up your agent · Agent notes · PDF guides · Token study · Changelog
Baton is a local daemon that owns your running apps, with an MCP server and a CLI in front of it. Your agent starts an app on a simulator or in a browser, applies each edit with one check_change call, and gets back only what is new: the reload result, error lines, failed requests and a screenshot, with an OK / NOT OK verdict. You see the same runs in your terminal, in the Baton app, and in the band above Claude Code's prompt, and you can press the same buttons. Baton reads the .vscode/launch.json, package.json, pubspec.yaml, Xcode and Gradle projects you already have.
0.2.10 is a public developer preview. Open an issue with what broke or what you wanted.
Requires Node.js 24+ on the machine that runs your apps. macOS, Linux and Windows.
npm install -g baton-run
baton setup # adds Baton to every coding agent installed on this machine
Restart your agent (or open a new chat) and ask it to "run the app and show me a screenshot".
Other ways in:
| Way | Command |
|---|---|
| Claude Code plugin | /plugin marketplace add kanumuri9593/Baton then /plugin install baton@baton |
| Codex plugin | codex plugin marketplace add kanumuri9593/Baton then codex plugin add baton@baton |
| VS Code or Cursor, one click | the install buttons at the top of this page |
| VS Code MCP gallery | search @mcp baton in the Extensions view (GitHub MCP Registry listing) |
| MCP server, no install | npx -y baton-run as the server command (pin with baton-run@0.2.10) |
| Pinned GitHub install | npm install -g github:kanumuri9593/Baton#v0.2.10 |
| From source | git clone https://github.com/kanumuri9593/Baton.git && cd Baton && npm install && npm run build |
baton setup edits only the baton entry in each tool's config, keeps a .baton-backup of every file it changes, and is safe to run again. baton setup cursor codex limits it to those tools, --dry-run previews, --remove undoes it.
Any MCP client that takes an mcpServers block:
{
"mcpServers": { "baton": { "command": "npx", "args": ["-y", "baton-run@0.2.10"] } } }
inspect_project → boot_device → run_target → wait_for → edit → check_change → fix → check_change
inspect_project (and list_targets) with cwd set to the absolute project path.boot_device if no simulator or emulator is up. With no name it lists what can boot.run_target, or run_workflow for an API plus a frontend, then wait_for. wait_for accepts up to 15 minutes, enough for a first native build.check_change. It applies the edit (hot reload for Flutter, HMR for web and React Native, restart for native and plain processes) and returns only what changed.NOT OK console/storefront action=none status=running 2280ms
new errors (1): [vite] Internal server error: Unexpected token (14:2)
Failed Flutter reloads return the compiler errors, not just DevFS synchronization failed:
lib/main.dart:419:19: Error: Expected ';' after this.
Screenshots cover iOS simulators, Android devices and web apps. For web, Baton opens the session URL in a throwaway headless Chrome, Edge or Brave (or BATON_CHROME) at viewport phone (a real 390×844 mobile layout), tablet, desktop or WIDTHxHEIGHT. Web captures are 1× by default, so a phone image is 390×844 (about 430 image tokens for a model); pass scale: 2 (--scale 2) when fine detail matters. check_change with screenshot: false returns text only but still loads a web page, so its console errors count. Simulator and device screenshots are returned at the device's own resolution.
Baton launches apps and reports evidence. It does not tap the UI or judge screenshots: a capture means an image was written, not that the screen is right. Pair it with Playwright MCP, Chrome DevTools MCP or a device-control MCP when a flow needs input.
29 tools: inspect_project, list_targets, list_sessions, list_checkouts, list_devices, boot_device, run_target, run_workflow, check_change, hot_reload, hot_restart, stop_session, forget_session, wait_for, read_logs, session_summary, screenshot, set_debug_flag, diagnose, list_network_requests, get_network_request, clear_network_requests, read_launch_config, write_launch_config, run_proof, list_proofs, list_run_history, show_dashboard and dashboard_action (the buttons on the live card that show_dashboard draws in hosts that support MCP Apps). Each carries MCP hints, so clients that honour them can skip the prompt for the 16 read-only tools.
| Agent | baton setup id | Guide |
|---|---|---|
| Claude Code (terminal, desktop app, VS Code) | claude (installs the plugin) | docs/clients/claude-code.md |
| Codex | codex | docs/clients/codex.md |
| Cursor | cursor | docs/clients/cursor.md |
| VS Code (GitHub Copilot agent mode) | vscode | docs/clients/vscode.md |
| Antigravity | antigravity | docs/clients/antigravity.md |
| Gemini CLI | gemini | docs/clients/gemini-cli.md |
| Windsurf | windsurf | docs/clients/windsurf.md |
| Claude Desktop (chat) | manual only | docs/clients/claude-desktop.md |
Agents without MCP can shell out to the same CLI. Every command exits non-zero on failure, and baton check --json gives the same verdict as check_change. Full agent notes: AGENTS.md. Crawler summary: llms.txt.
Printable guides to share: quick start, agent setup guide and FAQ.
The plugin draws Baton above the prompt while anything runs, in the terminal and in the desktop app. One row per run, with its device or URL, status, CPU and memory, and icon buttons:
| Button | What it does |
|---|---|
| ☰ | Show or hide that run's recent logs under its row |
| 🐞 | Debug: asks Claude to read the run's errors and logs, fix the cause and check_change |
| ▶ | Play: hot reload (or restart) a running app, resume a paused one, or run it again once it ends |
| ⏸ | Pause the app (macOS) |
| ⏹ | Stop. Once a run has ended this becomes ✕ dismiss |
| ⧉ | Bring that run's own simulator window (or its web page) to the front (macOS) |
The header has + (new run: puts /baton:run in the prompt) and the same ▶ ⏸ ⏹ ⧉ for every run at once. Bring all raises every device's window. /baton opens the same workspace in a side pane with longer logs. The band and pane read the same daemon as the MCP tools, so a run started by Claude, the CLI or the Baton app shows up everywhere. Details: docs/clients/claude-code.md.
| Framework | Hot reload (keeps state) | Restart | Notes |
|---|---|---|---|
| Flutter / Dart | ✅ real, via the daemon protocol | ✅ hot restart | Devices, DevTools, debug flags, screenshots (Flutter web too) |
| Next.js, Vite, Nuxt, Astro, Remix, Angular, CRA | HMR is automatic on save | ✅ reboots the dev server | Detects the real URL and readiness; phone, tablet and desktop screenshots |
| React Native / Expo | Fast Refresh is automatic | ✅ reload broadcast to dev clients | Talks to Metro's message socket |
| Native iOS (Xcode) | — | ✅ rebuild, reinstall, relaunch | Builds for the selected simulator, installs, launches, follows logs, screenshots |
| Native Android (Gradle) | — | ✅ rebuild, reinstall, relaunch | installDebug, starts the launcher activity, follows logcat, screenshots |
| Anything else | — | ✅ kill and respawn | Any launch.json or package.json script |
Capabilities are reported honestly. A Vite session does not claim Flutter's stateful hot reload, so the control panel greys the button out and agents get a clear refusal instead of a silent no-op.
Baton reads what you already have. No new config file is required.
.vscode/launch.json, read but never modified, so your IDE keeps working.claude/launch.json, same formatpackage.json: dev, start, serve and storybook scripts, with the package manager taken from your lockfilepubspec.yaml: Flutter projects with no launch.json still get a default.xcodeproj / .xcworkspace, shared schemes, Podfile, or Package.swiftsettings.gradle(.kts), the wrapper, application modules, or a lone AndroidManifest.xmlA nested ios/ or android/ folder picked on its own is a native target. Picking the Flutter or React Native root still runs the framework, which is what hot-reloads. Native sessions build, install and launch on the device you pick, then follow the app log. Restart rebuilds and relaunches.
baton init writes a .vscode/launch.json from what it detects (--claude for .claude/launch.json). See examples/ for small launch configs.
baton list # every ta冒頭だけを表示しています。続きはリポジトリで読めます