Actions exposed over MCP
Publish the site's Actions layer as an MCP server, so an external agent can use it — without opening more than it should.
- MCP
- TypeScript
- Cloudflare Workers
The studio's own site: showcase, journal and tutorials, built as a demonstration of the architecture it sells.
This site is its own first use case.
Its business logic does not live inside components: it is named in an Actions layer —
setTheme, setLocale, openService — invoked identically by the interface, soon by a
command palette, then by an agent. That is exactly what the Agent-Native Architecture
Advisory sells, and selling it without practising it seemed dishonest.
The rest follows the same rule: accessibility is a design constraint rather than a review pass, tests run against the built site rather than the dev server, and every structural decision is written into an ADR before it is coded.
Publish the site's Actions layer as an MCP server, so an external agent can use it — without opening more than it should.
Write an article in French, derive the English version and the metadata from it, without a model publishing anything on its own.
An orbiting expertise graph, animated and keyboard-navigable, that stays legible on a phone.