Skip to main content
Expose a private, scoped set of tools as a sub-MCP server. A sub-MCP app publishes a named subset of a server’s tools under its own slug — a second MCP endpoint carrying only the tools you list. Point a client at the slug and it sees just that set, not the whole server. Use it to scope a client to a private tool set. Private tool sets explains the model this builds on.

​
Register a sub-MCP app

Name the slug to mount under and the tools to expose with the repeatable --tool.
The app mounts under its slug and re-presents only the named tools. Registering the same slug again reloads it with the new tool set.

​
Inspect and remove

1

List the registered apps

List the sub-MCP apps and the tools each exposes.
2

Point a client at the slug

An MCP client connects to the sub-MCP endpoint the same way it connects to the main server, at the slug’s own mount: /app/{slug} — so the utilities app above answers at https://<your-server>/app/utilities. A tai sub-mcp register app is served over the streamable HTTP transport (the default), the same transport the main MCP endpoint uses. See MCP clients.
3

Unregister an app

A sub-MCP app is a projection, not a copy. It exposes the same live tools under a narrower surface — a tool removed from the main server disappears from every sub-MCP app that listed it.

​
See also