Skip to content
PRESHaiPRESHaiPRESHos Platform

Catalog

The catalog is the adopted tool inventory at /ai/tools: Tools and toolsets agents can call. The header counts total, active, and unadopted tools. Rows are platform-provided (Built-in source): the catalog side of capabilities, before tenant-specific installs.

  • Each row carries name, key, source, adopting-agent count, last called, 30-day calls, and status.
  • The agents column shows adoption. Tools with no agents are the gap between shipped and used.
  • Sort by name; filter by source, status, no-agents, or never-called. Add tool creates beyond the catalog.
  • Installed does not mean trusted or connected. Tools that reach external systems are only real for the tenant when the binding and MCP chain behind them is verified in-environment.
Catalog: tool inventory with name, key, source, adopting agents, calls, and status per row
  • The platform catalog (PRESHos-managed, requirePlatformOps where set) is the shipped side; tenant rows are the install side. MCP installs land via POST /api/v1/mcp-servers/install-from-catalog.
  • Destination catalog (target-catalog.ts) bounds where imported records may land (for example targetObject: 'work-items' with workItemTypeId); never the retired tasks/deliverables destinations.
  • Verify before use: fingerprint recheck and DNS-pinned guarded fetch for MCP, in-environment listing for connectors.

Treat /ai/tools as the source of truth for catalog surfaces. The calling layer: Toolsets. Tenant-side registries: MCP registry, Tool registry. Verification flow: Skills, tools and MCP.