Verified connector

Yaver

io.github.kivanccakmak/yaver

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

Install surfaces

How Yaver runs, per the official MCP registry entry.

Repository

Governed execution

How KLA gates calls to Yaver once it is connected.

A published policy defines which Yaver actions an agent may take and under what conditions. Each call passes through a policy gate at the tool-call boundary. Permitted actions execute, with the policy basis recorded. Flagged actions execute and are sampled for scheduled human review. High-stakes actions pause and route to a named reviewer on the Decision Desk. The call, the policy decision, and any approval are sealed as an evidence record.

Browse all connectors

KLA also governs the agent frameworks and model providers you already run. See integrations.

Yaver MCP connector