Mcph
io.github.YawLabs/mcph is a MCP server that hosts and routes all of your MCP tools from one cloud-managed install.
About
mcp.hosting (io.github.YawLabs/mcph) is a Model Context Protocol server that gives developers one install path to run and manage many MCP backends from the cloud instead of maintaining a growing local server list. You register it in Claude Code, Cursor, or other stdio-capable agents when you are stacking integrations during build and want a stable hub before you ship. The server advertises centralized provisioning so adding GitHub, databases, or custom tools does not require duplicate credentials on every laptop. It fits developers who treat agents as the primary interface and need agent-tooling infrastructure without a dedicated DevOps hire. Complexity is intermediate because you still choose which remote servers to attach and how auth flows. It is not a marketplace of skills; it is hosting and orchestration for MCP endpoints you already trust.
- 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
Mcph by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add mcph -- npx -y @yawlabs/mcphAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | @yawlabs/mcph |
|---|---|
| Transport | STDIO |
| Auth | None |
What it does
Centralize every MCP server behind one cloud-managed install so Claude Code or Cursor can reach tools without juggling local configs.
Who is it for?
Best when you're running Claude Code or Cursor with five or more MCP integrations and want one hub instead of editing config per repo.
Skip if: Skip if you only need a single local MCP server with no cloud dependency or air-gapped environments.
What you get
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
By the numbers
- 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
Recommended MCP Servers
나라장터 낙찰정보나라장터 낙찰정보서비스 Open API를 위한 로컬 MCP 서버나라장터 사전규격나라장터 사전규격정보서비스 Open API를 위한 로컬 MCP 서버나라장터 입찰공고나라장터 입찰공고정보서비스(공공데이터포털 data.go.kr) Open API를 감싼 로컬 MCP 서버
Accelerators36 tools for AWS infrastructure, security compliance, AI workflows, and ACI governance.
ACMSApple Container MCP Server (ACMS) provides access to Apple's container CLI tool on macOS3
Acronis MCPThe first real CLI for the Acronis Cyber Protect Cloud platform - every tenant, agent, and usage15How it compares
MCP hosting and routing layer, not an agent skill or a curated skill marketplace.
FAQ
Who is io.github.YawLabs/mcph for?
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.