Foundation 06

Choose which interfaces each object should have

REST, MCP, WebMCP, and CLI can share one model description while exposing different operations to different audiences.

Manifest

RESTMCPWebMCPCLIBrowser

Each interface reads the same declared model capabilities.

Expose only what each surface needs

A public HTTP API can be read-only while an internal CLI includes maintenance actions and an MCP server offers a narrow tool set.

REST routes and generated TypeScript clients.
MCP and WebMCP tools with shared names and JSON Schema inputs.
App-specific CLI resources and commands.
Browser collections backed by the generated REST client.

Treat WebMCP as a page surface

Register only the tools that make sense on the current page. They run through the signed-in browser session, so the server remains responsible for authentication, tenant scope, writable fields, and permissions.

Find every surface on the package page

Each package page keeps its description, components, playground entries, REST surface, MCP and WebMCP tools, and CLI notes together.