The wiring

One command and your agent publishes.

Into whatever you already use, without changing how you work — a plugin, an MCP connection, or a pipe from a CI job.

Install the plugin

One command sets up the agent side. It shows you a status table first, then asks before it touches anything — the config files it edits are yours.

Claude Code and Codex — both are registered by the same run; a missing one is reported rather than treated as a failure.
Status first, then consent — the ✓/✗ table comes before any question, and only the config-touching steps are asked about.
Clones are born registered — the registration is recorded in .mcp.json beside .vitrinka/project.json, so committing them means the next person who clones the repo is already connected.

Any MCP client

Connect over MCP and the board becomes a tool your agent can call directly — read and write, not just read. That is the difference between an agent that reports to a board and an agent that answers one.

Thirty-seven tools — boards, sets, sections, components, templates, questions, annotations and project memory — each one a call, not a scrape.
It can wait — wait_for_work blocks until a new annotation arrives, so a session parks on a board instead of polling it.
It can ask — boards carry questions with options, so the agent can put a decision to a human and read the answer back.

The workflow comes with it

Eighteen skills ship alongside the tools. The agent gets the procedure — how to capture a journey, service a board's queue, cut a release — rather than an API surface it has to be taught from scratch.

Capture and publish — screenshots, journeys, sessions and boards.
Service the queue — listen on a board, drain its annotations, push proof shots back.
Document and release — living docs, diagrams, page authoring and release notes.

When it drifts

Editors move their config, registries change shape, machines get reimaged. The health check is a first-class command rather than a support article.

vitrinka doctor — prints what is registered and what is not, wherever it lives.
doctor --fix — repairs the parts it can decide safely and leaves the rest to you.
vitrinka uninstall — removes everything it put there, for when the answer is no.

Just curl

Anything else — CI, a script, a machine with no plugin at all — publishes a whole set with a tar pipe. There is no SDK to adopt.

A tar pipe is enough — one HTTP call from any CI job that can produce files.
Tokens are mintable and revocable — and both events are recorded in the audit trail.