mount() mirrors an in-process child into a parent, and createProxy() wraps a remote MCP server as a mountable FastMCP instance.
This page is under construction. The outline below sketches what it will cover.
- Mounting semantics — live mirroring (components registered on the child after
mount()appear in the parent immediately, withlist_changednotifications); prefixing renames tools/prompts to${prefix}_${name}but never alters resource URIs; mounting cascades through grandparent chains. - Why it composes cleanly — mounted components land in the parent’s own registries, so transforms, middleware, and auth apply to them identically.
- Proxying —
createProxy({ type: 'stdio' | 'http', ... })returns a plainFastMCPthat forwards all calls verbatim; closing the parent closes the proxied connection. - Choosing between mount and proxy — in-process vs. remote, and combining both behind one gateway.