Yaw MCP

Spec Support Unverified First-party Confidence: Good (0.85)

MCP server · by YawLabs · Developer Tools, Infrastructure and DevOps · Last verified: 2026-08-27

Yaw MCP is an MCP server published by YawLabs; its MCP spec-revision support has not been verified yet. It is the first-party server from YawLabs. Last verified 2026-08-27.

Does Yaw MCP support the current MCP specification (2026-07-28)?

Undetermined. We have not verified which MCP specification revision Yaw MCP supports (as of 2026-08-27).

Is Yaw MCP a first-party (official) MCP server?

Yes. Yaw MCP is the first-party MCP server published by YawLabs (last verified 2026-08-27).

How do I connect to Yaw MCP?

Yaw MCP is available via the package npm:@yawlabs/mcp, the official MCP Registry under io.github.YawLabs/mcp, the source repository at https://github.com/YawLabs/mcp. Authentication: none. Transports: stdio.

When were Yaw MCP's facts last verified?

2026-08-27. Each fact on this page links to the sources used to verify it.

Yaw MCP is an orchestrator: one local stdio server that fronts every other MCP server a user runs, so each AI client (Claude Code, Claude Desktop, Cursor, VS Code) points at a single connection and the underlying servers load lazily from a shared bundles.json instead of per-client configuration blocks. It runs entirely locally with no account, storing credentials in an encrypted vault; its catalog scores entries against the 88-test mcp-compliance suite. Ranked #158 in the MCP 500 at the 2026-08-14 snapshot. YawLabs' non-orchestrator servers are cataloged separately.

Spec revision support has not been verified for this entry.

How was this verified, and what are the sources?

Verified 2026-08-27 · method: registry-record · confidence 0.85 (Good).