This MCP server bridges Claude with Yaver's phone-first development workflow. It exposes 473 tools for managing React Native projects that start as phone sandboxes and promote to your dev machine or cloud. You can export, import, and push phone projects, trigger Hermes reloads to iOS or Android, and orchestrate remote dev boxes running coding agents while streaming build output back to mobile. The primary path is phone sandbox to your hardware to optional Yaver Cloud, with the MCP layer handling project state, bundle compilation, and cross-device coordination. Reach for this if you're prototyping React Native apps from mobile and want Claude to manage the full build, test, and deployment chain across your phone, WSL box, or remote server without jumping to Firebase or Supabase first.
Yaver is a local-first developer toolkit for driving coding agents, previews, feedback, and deploy loops from your phone.
Your code stays on your machine. The mobile app is the remote control; the yaver agent runs on your Mac, Linux box, WSL machine, Pi, or VPS; the SDK captures feedback from your own dev builds.
npm install -g yaver-cli
yaver auth
yaver serve
For headless machines:
yaver auth --headless
yaver serve
If an AI coding agent is setting Yaver up for you, read the canonical machine guide first:
curl -s https://yaver.io/llms.txt
yaver serve on your own machine.| Path | Purpose |
|---|---|
desktop/agent/ | Go agent, CLI surfaces, local API, relay/P2P/runtime integrations |
mobile/ | React Native mobile app and native preview container |
web/ | Next.js marketing site and dashboard |
backend/convex/ | Hosted identity, session, and device-discovery metadata |
relay/ | QUIC relay service |
sdk/ | Public SDKs and feedback clients |
demo/ | Small fixture apps used to test SDK and push flows |
demo-videos/ | Source notes for the landing/demo clips |
docs/ | Architecture notes, setup guides, audits, handoffs, and planning material |
Markdown in this repo is context, not source of truth. If a doc and the code disagree, trust the code and fix the doc in the same change.
# Web dashboard / landing
cd web
npm install
npm run dev
# Go agent tests
cd desktop/agent
go test ./...
Run the narrower package tests for the area you change; the full repo spans Go, Node, React Native, Swift, Kotlin, Flutter, Unity, and embedded C work.
Core Yaver code is under FSL-1.1-Apache-2.0. SDK packages are Apache-2.0 where marked. See docs/planning/LICENSING.md.
YAVER_HEADLESSSet to 1 to force device-code OAuth instead of opening a browser (useful in remote / WSL / sandboxed environments).