Reference

REST, MCP, WebMCP, and CLI

Each generated interface is a view over the capabilities declared on your object. They share metadata but can expose different action sets.

Manifest

RESTMCPWebMCPCLIBrowser

Each interface reads the same declared model capabilities.

REST

Generated SvelteKit routes use manifest schemas, writable-field policy, authentication, tenant scope, and operation permissions. Package pages show the representative route shape.

MCP

Tool names, descriptions, and JSON Schema inputs are generated from explicitly included model actions. Agent and persona tool ceilings can narrow what a principal may call.

WebMCP

The browser registers selected generated descriptors with document.modelContext. Calls use the signed-in page session and generated REST fetchers; the server remains the security boundary.

CLI

Application CLIs turn manifest resources into predictable commands and can add model-specific operations. The framework CLI also owns migration, scanning, generation, and introspection workflows.

smrt app <operation> owns the application lifecycle: install, setup, start, stop, recover, doctor, open, backup, export, import, migrate, worker, and dev or build. A generated project maps each package.json script to one of them instead of carrying copied scripts.
smrt cookbook validate and smrt cookbook apply check a cookbook against the recipe manifests and create a project from it. smrt kitchen serves the planner on localhost and applies the cookbook it produces.