Skip to main content
Mount an existing external MCP server so its tools appear in your running server. The runtime mounts other MCP servers and re-presents their tools as its own. You declare each server in the manifest’s mcp section; the runtime probes it at startup and binds its tools alongside your local ones.

​
Declare a server in the manifest

Each mcp entry names one server. Set exactly one transport per entry — the runtime infers the transport from whichever field you set:
  • url for a remote HTTP or SSE server (with optional headers),
  • uds for a Unix domain socket,
  • command (plus args / env) for a stdio server the runtime launches.
manifest.yml
Use include / exclude on an entry to expose only a subset of the mounted server’s tools.

​
Inspect and reload

1

Check binding status

Snapshot the live MCP binding state — which servers attached and which were skipped by a failed viability probe.
2

Replace the set at runtime

Write the full replacement mcp list to a JSON file, then apply it. This hot-reloads the section without restarting the server.
3

Reload one server

Re-probe a single server by its manifest title and re-attach it if it is viable.
A server that fails its viability probe is skipped, not fatal — the rest of the manifest still loads. Inspect skipped servers under tai mcp status.

​
See also