Yaver
Control your dev machine from your phone through a P2P MCP layer so agents can hot-reload, build, deploy, use git, and manage tunnels while you are away from the desk.
Overview
Yaver is a MCP server for the Build phase that links your phone and dev machine over P2P so coding agents can hot reload, build, deploy, and manage git and tunnels remotely.
What is this MCP server?
- Phone-to-dev-machine P2P control plane with MCP tools for hot reload, builds, deploys, git, tunnels, and sessions
- Resumable headless OAuth device-code flow that survives agent tool-call timeouts without re-prompting
- Auto-registers in Claude Code, Claude Desktop, Codex, Cursor, Windsurf, and Zed on first sign-in
- Provider-agnostic design for any coding agent using MCP
- npm yaver-cli via npx with optional YAVER_HEADLESS=1 for device-code OAuth
- npm package yaver-cli version 1.99.99
- Auto-registration targets include Claude Code, Claude Desktop, Codex, Cursor, Windsurf, and Zed
- Install guide https://yaver.io/docs/mcp
Community signal: 4 GitHub stars.
What problem does it solve?
You cannot steer local builds and deploys when you are mobile, and generic remote access does not expose structured MCP tools agents already know how to call.
Who is it for?
Solo builders who live in agent-driven workflows and want credible phone-side control of the same machine their MCP client uses.
Skip if: Teams that ban remote machine access, need only cloud CI dashboards, or will not complete OAuth/device sign-in.
What do I get? / Deliverables
After Yaver is registered, your agent—and Yaver’s mobile side—can run structured dev-machine actions like reload, build, deploy, and tunnel setup without you sitting at the IDE.
- Registered Yaver MCP tools on the dev machine
- Phone-accessible agent actions for reload, build, deploy, git, and tunnels
Recommended MCP Servers
Journey fit
Agent-tooling under Build is the shelf because Yaver’s headline is extending coding agents with a control plane to your machine—not a marketing or analytics product. Hot reload, builds, deploys, git, tunnels, and sessions are day-to-day implementation and delivery actions agents trigger via MCP tools.
How it compares
P2P dev-machine MCP control plane, not a hosted cloud IDE or static skill markdown.
Common Questions / FAQ
Who is Yaver for?
Provider-agnostic coding-agent users—especially on Claude Code, Cursor, Codex, or Windsurf—who want mobile-triggered builds and deploys on their own hardware.
When should I use Yaver?
Use it when you need hot reload, builds, deploys, git, or tunnels driven by an agent while away from your desk, or when headless OAuth must survive long MCP tool timeouts.
How do I add Yaver to my agent?
Follow https://yaver.io/docs/mcp: run the yaver-cli npm package (npx), complete sign-in so it auto-registers in your editor, and set YAVER_HEADLESS=1 if you need device-code OAuth without a browser.