40 Capability Mounting

40 Capability Mounting

Source: docs/design/40-capability-mounting.md

Status: implemented (D91)

A capability = one catalog connection (app:{slug}) or custom MCP server (mcp:{serverId}).

Reply turns only get a <capabilities> directory + read-only two-pack capability_search / capability_call — they do not mount every external tool.

Tasks declare start_task.capabilities (≤8). Task start mounts only declared capabilities (inline if ≤40 tools, else fold into the two-pack); others reachable via the two-pack fallback.

Mail is special: mail_request_setup always registered; other mail_* tools only when bindings exist. Does not appear in the capability directory.