Mcph
Centralize every MCP server behind one cloud-managed install so Claude Code or Cursor can reach tools without juggling local configs.
Overview
io.github.YawLabs/mcph is a MCP server for the Build phase that hosts and routes all of your MCP tools from one cloud-managed install.
What is this MCP server?
- Single npm install (@yawlabs/mcph) with stdio MCP transport
- Cloud dashboard to add, update, and route multiple MCP servers
- Version 0.57.1 package aligned with MCP server schema 2025-12-11
- Reduces per-project MCP.json sprawl for indie agent workflows
- Managed hosting so local machine stays thin while tools run remotely
- Published package version 0.57.1 on npm as @yawlabs/mcph
- Uses MCP server schema dated 2025-12-11
- stdio transport type in server manifest
What problem does it solve?
Local MCP configs multiply with every new tool, breaking agent setups across machines and side projects.
Who is it for?
Solo builders running Claude Code or Cursor with five or more MCP integrations who want one hub instead of editing config per repo.
Skip if: Teams that only need a single local MCP server with no cloud dependency or air-gapped environments.
What do I get? / Deliverables
After you add mcph, one stdio connection can reach a managed set of MCP servers you control from mcp.hosting.
- One stdio MCP entry pointing at @yawlabs/mcph
- Central registry of attached MCP servers via mcp.hosting
- Repeatable agent config across dev machines
Recommended MCP Servers
Journey fit
How it compares
MCP hosting and routing layer, not an agent skill or a curated skill marketplace.
Common Questions / FAQ
Who is io.github.YawLabs/mcph for?
Indie and solo developers who use AI coding agents daily and need many MCP servers without repeating local installs.
When should I use mcp.hosting?
Use it during build and operate when your MCP server list outgrows one machine or you want cloud-side updates without redeploying every client.
How do I add io.github.YawLabs/mcph to my agent?
Install @yawlabs/mcph from npm, add the stdio server entry to your agent MCP config, then connect your mcp.hosting account to register downstream servers.