A CLI that runs MCP servers on your machine, no account required. Sync your bundles across machines with Pro. Team-shared bundles + audit log included in Yaw Business.
yaw mcp inside Yaw Terminalnpm install -g @yawlabs/mcp yaw mcp install claude-code yaw mcp doctor
yaw mcp command, which forwards to the yaw-mcp CLI on PATH. One-time npm install -g @yawlabs/mcp wires it up. Future Terminal builds will bundle the CLI directly so the npm step disappears.npm install -g @yawlabs/mcp yaw-mcp install claude-code yaw-mcp doctor
~/.yaw-mcp/bundles.json on your disk.
yaw mcp dispatch ranks your servers against the current task and loads only what is needed instead of keeping every tool description in your AI client's context window.
YAW_MCP_MIN_COMPLIANCE=B and the CLI refuses to activate anything below the bar. The grade renders inline on every discover output - the trust signal is visible without opting in first.
yaw mcp sync push uploads your server schema (env values stripped) to a private store. yaw mcp sync pull mirrors it onto another machine. Set up once, use everywhere.
yaw mcp sync pull.
yaw mcp install <client> wires up the launch entry in the correct config file for the OS - no hand-editing JSON.
Pick what you need. Pro and Yaw Business unlock the same underlying CLI - Free is not a degraded version, it is the same product without cloud sync.
~/.yaw-mcp/bundles.jsonyaw mcp stats commandNo. Free runs entirely from a JSON file on your machine. The CLI never phones home in Free mode - no telemetry, no opt-in pings, no account check on startup. You only need a license key if you want to sync bundles across machines (Pro) or share them with a team (Yaw Business).
Yaw MCP is the rebrand of what previously shipped as mcp.hosting and the @yawlabs/mcph CLI. The old hosted SaaS is being sunset; the local-first CLI is the new product. Existing mcp.hosting URLs redirect to yaw.sh/mcp; the old @yawlabs/mcph package is deprecated and points at @yawlabs/mcp.
A bundle is the set of MCP servers Yaw MCP will load on startup. Each server entry has the standard MCP shape - a namespace, a command, args, env vars, and either a transport or a URL. The local file is ~/.yaw-mcp/bundles.json (user-global) or <project>/.yaw-mcp/bundles.json (project-local, overrides user-global). The CLI's install meta-tool edits this file for you.
Phase 6a (shipping now): the sync push command strips env VALUES before upload - only the schema (which env vars each server expects) goes to the server. Your secrets stay on each machine. Phase 6b will add an encrypted vault (mcp_secrets) where you can opt in to syncing the values too, encrypted with a passphrase you control. The server never sees the plaintext either way.
Yes. Yaw MCP is itself an MCP server that launches over stdio. yaw mcp install <client> writes the correct launch entry into the client's config file (correct path for your OS, correct JSON shape). Supported clients: Claude Code, Claude Desktop, Cursor, VS Code. Any client that speaks the MCP stdio protocol will work even if not in that list.
The architecture supports it for free - both products share the same Netlify Functions backend, the same license key format, and the same HMAC session cookie. The team-shared resources (connections / commands / runbooks for Terminal; bundles / secrets / audit log for MCP) are conceptually the same thing: team-shared dev tooling state. One license key, two product surfaces, simpler pricing.
Yaw MCP IS self-hosted by default. The Free tier runs entirely on your machine with no backend dependency. The only thing the Pro / Yaw Business backend does is sync - and that backend (Netlify Functions on yaw.sh) has no per-customer footprint, just shared blob storage keyed by license-order-id. There is no "deploy your own Yaw MCP backend" product because the sync layer is intentionally a hosted-only convenience, not a system you'd want to run yourself for one team.