Capability Discovery

Discover capabilities without confusing documentation with runtime availability.

Aboard treats MCP as a Connector role within the unified Plugin lifecycle. A Plugin may declare tools, Agents, UI contributions, or Connectors, but declaration does not grant execution permission.

For each capability, preserve its stable identifier and version, supplying Plugin or Provider, dependencies, Workspace context, permissions, credentials, side effects, authority, and installation/activation requirements.

Docs Search MCP retrieves documentation. Runtime MCP transports runtime capabilities. Aboard Host is the local execution authority. The documentation site remains read-only.