Y
YawLabs/mcp
MCP orchestrator, one install, all your MCP servers
在 GitHub 查看 ↗链接已于 2026-11-14 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"yawlabs-mcp": {
"command": "npx",
"args": ["-y", "@yawlabs/mcp@latest"]
}
}
}解析自我们于 2026-11-12 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"yawlabs-mcp": {
"command": "npx",
"args": ["-y", "@yawlabs/mcp@latest"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio yawlabs-mcp -- npx -y @yawlabs/mcp@latest
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 1 ★ · YawLabs/mcp · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-11-13 · 最近见到 2026-11-14 · 共见到 2 次 · 被 2 个来源列出
- 评分构成
- 综合分 203 · 1 ★ · 2 个来源 · repo
- 安装
npx -y @yawlabs/mcp@latest
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx -y @yawlabs/mcp@latest。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: 开源项目。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
YawLabs/mcp；我们收录于 2026-11-13；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# @yawlabs/mcp
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
One install. Every MCP server. Managed from one place.
Yaw MCP (the yaw-mcp CLI) is an MCP server that fronts every other MCP server you use. Point each AI client (Claude Code, Claude Desktop, Cursor, VS Code) at it once, and your servers load lazily from a single connection instead of a hand-edited mcpServers block per client.
It runs entirely on your machine. No account, no sign-in, no telemetry -- your servers live in a local bundles.json and your credentials in a local encrypted vault. Running as an MCP server, its only outbound calls are two background npm checks: one for its own updates (YAW_MCP_AUTO_UPGRADE=0 to disable) and, if you have run yaw-mcp sidecars install, a once-a-day check that the managed sidecar packages are current (YAW_MCP_SIDECAR_REFRESH=0 to disable). One more is conditional: if a configured server launches through uv/uvx and uv is not on your PATH, yaw-mcp downloads Astral's uv release from GitHub once and caches it (see Runtime detection & uv bootstrap). yaw-mcp add, search and try fetch the public server catalog on demand. Nothing else leaves your machine.
It earns its keep when you hit any of these:
More than one client. Define a server once in bundles.json; every client on the machine picks it up. No copy-pasting the same JSON into four config files. (Sync bundles.json across machines with your dotfiles if you want it everywhere.)
Tool-context bloat. The dispatch meta-tool ranks your servers against the task and loads only the top match. A 30-server setup keeps a handful of tools in context at a time instead of hundreds.
Tokens you'd rather not leave in disk configs. Credentials live encrypted in a local vault and inject at spawn time. Rotate once; every client picks up the new value.
A trust signal before you activate. Every scored server shows an A-F compliance grade. Set YAW_MCP_MIN_COMPLIANCE=B to refuse anything below.
One client, a few servers? claude mcp add is fine -- yaw-mcp's value shows up when that setup stops scaling.
## How it works
Your MCP client (Claude Code, Cursor, ...)
| single stdio connection
@yawlabs/mcp --lazy load--> GitHub | Slack | Stripe | ... (your servers)
1. Add servers with yaw-mcp add (or edit ~/.yaw-mcp/bundles.json directly).
2. yaw-mcp reads that file on startup.
3. The model uses a handful of meta-tools to control which servers' tools are in context. Adding a server puts it on your list; loading it brings its tools into the session.
| Meta-tool | What it does |
| mcp_connect_dispatch | Describe a task in plain English; picks the best server, loads its tools, exposes them in one call. The fast path. |
| mcp_connect_discover | List available servers, optionally ranked by a context string. Auto-loads the top match when one clearly wins. Tool-name lists are capped at five per server; pass server for one server's full list. listOnly: true (for client UIs) returns the same listing with no side effects: no auto-load, no idle tick, no install suggestions. |
| mcp_connect_activate / deactivate | Load / unload specific servers by namespace. |
| mcp_connect_read_tool | Return one tool's schema without loading its server. |
| mcp_connect_find_tool | Search every installed server's tools by what they do, from cache: nothing is loaded and no server is contacted. A hit on a loaded server carries its full schema. |
Yaw MCP (the yaw-mcp CLI) is an MCP server that fronts every other MCP server you use. Point each AI client (Claude Code, Claude Desktop, Cursor, VS Code) at it once, and your servers load lazily from a single connection instead of a hand-edited mcpServers block per client.
It runs entirely on your machine. No account, no sign-in, no telemetry -- your servers live in a local bundles.json and your credentials in a local encrypted vault. Running as an MCP server, its only outbound calls are two background npm checks: one for its own updates (YAW_MCP_AUTO_UPGRADE=0 to disable) and, if you have run yaw-mcp sidecars install, a once-a-day check that the managed sidecar packages are current (YAW_MCP_SIDECAR_REFRESH=0 to disable). One more is conditional: if a configured server launches through uv/uvx and uv is not on your PATH, yaw-mcp downloads Astral's uv release from GitHub once and caches it (see Runtime detection & uv bootstrap). yaw-mcp add, search and try fetch the public server catalog on demand. Nothing else leaves your machine.
It earns its keep when you hit any of these:
More than one client. Define a server once in bundles.json; every client on the machine picks it up. No copy-pasting the same JSON into four config files. (Sync bundles.json across machines with your dotfiles if you want it everywhere.)
Tool-context bloat. The dispatch meta-tool ranks your servers against the task and loads only the top match. A 30-server setup keeps a handful of tools in context at a time instead of hundreds.
Tokens you'd rather not leave in disk configs. Credentials live encrypted in a local vault and inject at spawn time. Rotate once; every client picks up the new value.
A trust signal before you activate. Every scored server shows an A-F compliance grade. Set YAW_MCP_MIN_COMPLIANCE=B to refuse anything below.
One client, a few servers? claude mcp add is fine -- yaw-mcp's value shows up when that setup stops scaling.
## How it works
Your MCP client (Claude Code, Cursor, ...)
| single stdio connection
@yawlabs/mcp --lazy load--> GitHub | Slack | Stripe | ... (your servers)
1. Add servers with yaw-mcp add (or edit ~/.yaw-mcp/bundles.json directly).
2. yaw-mcp reads that file on startup.
3. The model uses a handful of meta-tools to control which servers' tools are in context. Adding a server puts it on your list; loading it brings its tools into the session.
| Meta-tool | What it does |
| mcp_connect_dispatch | Describe a task in plain English; picks the best server, loads its tools, exposes them in one call. The fast path. |
| mcp_connect_discover | List available servers, optionally ranked by a context string. Auto-loads the top match when one clearly wins. Tool-name lists are capped at five per server; pass server for one server's full list. listOnly: true (for client UIs) returns the same listing with no side effects: no auto-load, no idle tick, no install suggestions. |
| mcp_connect_activate / deactivate | Load / unload specific servers by namespace. |
| mcp_connect_read_tool | Return one tool's schema without loading its server. |
| mcp_connect_find_tool | Search every installed server's tools by what they do, from cache: nothing is loaded and no server is contacted. A hit on a loaded server carries its full schema. |
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/yawlabs-mcp/)
- 来源
- github · https://github.com/YawLabs/mcp
- 按领域浏览
- 开源项目
- Traction
- 1 ★
- 收录来源
- 2 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。