Operate Products through CLI and MCP

Agents can discover and manage optional Products through the CLI and typed MCP tools. Use atoll product list and get to inspect authorized metadata. Create, update, archive and restore use the existing organization owner/admin permissions. CLI references accept a Product UUID or an unambiguous exact name; remote MCP tools use the UUID returned by discovery.

Keep project access and lifecycle independent

Use atoll project set-product with --product to attach or move a project, or --none to detach it. Both MCP profiles expose the same operation with an explicit nullable Product ID. Product archive changes no project or task state, and archived projects retain the narrow affiliation operation. Product detail never expands inaccessible sibling projects or counts.

Select Product strategy ownership

Project lists and goal, KPI and initiative lists accept Product filters. Strategy create/update operations can select a Product or Organization ownership. CLI uses --product none; MCP writes use product_id: null. Omitted inputs retain existing behavior. Human member ownership stays separate, and existing goal compatibility checks, metric history and execution links remain authoritative.

The public plugin and full/private MCP profile expose typed Product discovery, management and affiliation tools. Public calls retain explicit profile selection. These source capabilities do not by themselves publish an npm package or update a provider marketplace installation; package publication and provider acceptance remain separate release steps.