Yaver

Name: Yaver
Author: kivanccakmak

by kivanccakmakversion 1.99.309i★ –iRuns on your computer

Registry nameio.github.kivanccakmak/yaver

Install

Overview

Description from the maker (original English)

Phone-first local dev MCP for Claude Code and Codex: install Yaver, pair mobile, run, build, deploy.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: YAVER_HEADLESS

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "yaver": {
      "command": "npx",
      "args": [
        "-y",
        "yaver-cli"
      ],
      "env": {
        "YAVER_HEADLESS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add yaver --env YAVER_HEADLESS=your-value -- npx -y yaver-cli

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "yaver": {
      "command": "npx",
      "args": [
        "-y",
        "yaver-cli"
      ],
      "env": {
        "YAVER_HEADLESS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "yaver": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "yaver-cli"
      ],
      "env": {
        "YAVER_HEADLESS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

YAVER_HEADLESS env
Set to 1 to force device-code OAuth instead of opening a browser (useful in remote / WSL / sandboxed environments).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account kivanccakmak, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 1396 servers in this category
Published to the registry more recently than 33% of the other 1396 servers in this category
Basic checks equal to or better than 100% of the other 1396 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Yaver safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.99.309) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Watch the full demo →

What Yaver is

AI writes the code in seconds. The loop around it — build, install, reproduce, describe what's wrong, get back to the agent — still takes hours. Yaver closes that loop.

The yaver agent runs on hardware you already own: a Mac, a Linux box, a WSL machine, a Pi, or a VPS. Your coding agent works there, against your real repo. Every other surface — phone, watch, TV, car, AR/VR, browser — is a remote control and a preview target for that one machine.

It runs on the AI subscription you already pay for — no token markup, and your code never leaves your machine.

iOS and Android are the deepest path today. Watch, TV, car, and AR/VR surfaces live in this repo and share the same core.

Quick start

npm install -g yaver-cli

yaver auth yaver serve

On a headless box (Pi, VPS, SSH-only), yaver auth --headless prints a short code and a URL you can open from any browser.

npm is the only supported install path, on macOS (Apple Silicon + Intel), Linux (x64 + arm64), and Windows via WSL2. It downloads a signed, notarized agent binary for your platform.

Then grab the app and pair it with that machine:

Open Yaver, pick a project from your dev box, preview it on your phone, shake to vibe-code — fix a bug, ship a small feature, or tweak a style — and a fresh bundle lands in seconds. One screen, real device, no extra hardware.

Install or use it from your coding agent

Install the CLI directly, or register Yaver as an MCP server so Claude Code, Codex, or opencode can drive your machine from chat. MCP does not need a global install first — npx pulls the server on first run.

# direct CLI

npm install -g yaver-cli yaver auth

or as MCP

Claude Code

claude mcp add --scope user yaver -- npx -y yaver-cli yaver-mcp

Codex

codex mcp add yaver -- npx -y yaver-cli yaver-mcp

opencode

npx -y -p yaver-cli yaver mcp setup opencode

then, in the agent chat:

call yaver_lazy_setup

To add Yaver to an existing Expo app, give the agent the app directory and ask it to call yaver_sdk_integrate. The direct deterministic equivalent is:

npx -y yaver-cli integrate --dir /path/to/app --framework expo --verify quick

This installs compatible dependencies, mounts the in-app Yaver surface, wires the Expo plugin, and verifies the project. It does not choose a bundle ID, configure your app's own authentication, deploy, or publish anything.

For a Yaver-generated Expo + Convex starter that needs AI, the agent can then call yaver_openrouter_integrate at the monorepo root. It adds an authenticated, cost-bounded HTTP/SSE seam and React Native stream helper while keeping the OpenRouter key server-side—no polling and no database write per token.

Already installed globally? yaver mcp setup claude-code (or codex / opencode) writes the same entry, and yaver auth auto-registers every installed runner on first sign-in. Yaver is published to the official MCP registry as io.github.yaver-io/yaver. Codex Desktop can also load the repo-local plugin in plugins/yaver.

Full tool list and HTTP/remote setup: [MCP guide](https://yaver.io/docs/mcp).

How it works

Start yaver serve on your own machine.
Pair a surface — the mobile app, the web dashboard, or another Yaver client.
Send a task to your coding agent from whichever surface is nearest.
Watch terminal, build, and reload progress stream back live.
Push the fix to a real device, or deploy from your own machine when it's ready.

The CLI, agent, relay, and backend are all self-hostable. Client apps currently reach you through a thin hosted coordination plane for identity and device discovery; full client self-host is on the way.

For remote access, Yaver Relay is the default path. The free shared relay is for light personal use and has fair limits; the relay implementation is open source if you want to run your own. Relay Pro is the optional $9/month managed lane with higher account-wide transfer limits. It connects to the machine or VPS you already control; it does not include hosted compute or an AI subscription.

What works today

Drive Claude Code, Codex, OpenCode, Aider, Goose, or another terminal agent from the Yaver agent.
Push React Native / Expo bundles to a paired phone through the native Hermes path.
Capture dev-build feedback with screenshots, logs, and replay context.
Stream task, build, and reload progress to mobile or the web dashboard.
Keep peer discovery, relay, and vault flows local-first.
Build against SDKs and examples for React Native, Flutter, web, Unity, Go, Python, and JS/TS.

What it costs

A solo developer can start with the open-source stack at $0.

Component	Runs on	Cost
Yaver CLI + agent	Your dev machine	$0
Yaver surface apps	iOS / Android / watch / TV / car / AR/VR	$0
Web dashboard	Browser	$0
Backend on your own machine	Your Mac / Linux / WSL / VPS	$0 + your hardware
Yaver shared relay	Yaver-hosted, fair-use limited	$0
Relay Pro	Managed account-private lane on shared relay hosts	$9/month
AI models (Ollama)	Your GPU or CPU	$0

The open-source stack includes the mobile app, CLI, agent, web dashboard, SDKs, and relay implementation. Yaver's shared relay is available with fair limits for getting started. Your coding agent brings its own login or subscription — Yaver never resells tokens.

V1 is focused on your own devices and self-hosted machines. Relay Pro is the only paid launch product; all client surfaces, browser/Hermes lanes, MCP and library integration, and the feedback SDK are included. Yaver does not sell a hosted coding workspace in this release.

Repository map

Path	Purpose
`desktop/agent/`	Go agent, CLI surfaces, local API, relay/P2P/runtime integrations
`mobile/`	React Native mobile app and native preview container
`watch/`, `wear/`, `tvos/`	Apple Watch, Wear OS, and Apple TV client surfaces
`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

Deploying Yaver

Use exactly one local entrypoint:

./deploy/deploy.sh <target> [options]

Targets are all, backend, cloudflare, ios, android, npm, and mcp with aliases listed by ./deploy/deploy.sh --help. The entrypoint delegates to the maintained vault-aware scripts and yaver deploy commands, but gives humans, agents, and MCP one path so deploys do not drift.

Deploys are owner-only. The script refuses group/other-writable repo or script paths before touching Convex, Cloudflare, App Store Connect, Play Console, npm, or MCP registry credentials.

This repo is the monorepo

Yaver is one monorepo — this one. Agent, CLI, mobile, watch, TV, car, AR/VR, web, relay, backend, and SDKs all live here and ship together. Splitting them would only buy version skew between surfaces that have to agree.

Everything else in the yaver-io org is a validation / use-case app — something whose only job is to exercise Yaver from the outside. Those are separate repos precisely because they must be clonable, buildable, and breakable on their own, exactly as a user's project is. If they lived in here they'd inherit this repo's tooling and stop being an honest test.

The rule: product code goes in this repo; anything that tests the product from outside gets its own repo.

Validation apps

The apps that prove Yaver works live in their own repos, not in this one. They are local-only todo apps — no backend, no accounts, no network — and they are deliberately boring, because they are the control.

The same todo app is built five ways. Yaver reaches each one differently, so when the loop feels different across stacks, it is the transport that differs and not the app:

Repo	Stack	How Yaver reaches it
yaver-todo-rn	Expo / React Native	Hermes — the agent compiles an HBC bundle and the container swaps it in place
yaver-todo-kt	Native Android (Kotlin)	native-webrtc — runs on a build host, H.264 streamed to the phone, taps sent back
yaver-todo-swift	Native iOS (SwiftUI)	native-webrtc — same, macOS build host only
yaver-todo-flutter	Flutter / Dart	native-webrtc — Dart has no Hermes equivalent
yaver-todo-web	Next.js	dev server — HMR through Yaver's relay path

Hermes is React-Native-only: native and Flutter apps compile to real binaries and can never be loaded into the Yaver container. That is why three of the five exist — they are the only honest way to exercise the streaming path.

They are separate repos so they can be cloned, built, and broken without touching this one. Each README states what works and what doesn't per stack, including where a feedback SDK does not exist yet.

Documentation

Docs index · Setup · Contributing · Runtime architecture · Protocol · Feedback SDK · Security · License

If an AI coding agent is setting Yaver up for you, point it at the canonical machine guide first:

Only the beginning is shown; read the rest in the repo

Yaver

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

What Yaver is

Quick start

Install or use it from your coding agent

or as MCP

Claude Code

Codex

opencode

then, in the agent chat:

How it works

What works today

What it costs

Repository map

Deploying Yaver

This repo is the monorepo

Validation apps

Documentation