One MCP server.Many upstreams. Per-client control.
MCP Daddy sits between your clients and upstream MCP servers, giving you a simple way to expose only the tools a client should see.
How it works
Think of MCP Daddy as a proxy: upstream servers on one side, your MCP clients on the other. For each client, you pick what upstreams (and therefore which tools) are visible.
Upstreams
stdio MCP servers
Each upstream runs as a local process. MCP Daddy launches them with the right command, args, and env.
MCP Daddy
Profiles + routing
A single MCP endpoint that aggregates, filters, and routes tool calls based on a selected client profile.
Clients
Cursor, Claude Desktop, etc.
Clients connect once. They see only what the profile allows, and call tools through MCP Daddy.
Security & privacy
MCP Daddy is designed to be local-first. It does not make security promises it cannot keep, but it does make dangerous actions explicit.
Local by default
Runs on your machine and connects to upstreams as local processes unless you configure otherwise.
Consent before commands
Before executing a run-command request, the UI shows the exact command and args and requires explicit approval.
Localhost safety
When enabled, downstream endpoints are intended to bind to localhost and can enforce per-client tokens and origin checks.
Roadmap
MVP
- Client profiles with allowlists (per-upstream)
- Full vs compact tool exposure modes
- Upstream presets + test connection
- Consent dialog for command execution
Future
- Optional sync/login for profiles and presets
- Safer secret storage (beyond plain JSON)
- Team sharing and audit-friendly activity logs