Agent and MCP integration

Today, a developer integrating Livstick usually has an agent working alongside them, reading the docs and writing the code. This page describes what Livstick makes available so that agent works from facts instead of guesses.

What already exists

Three things are true today, and an agent can rely on all three without asking anyone to confirm them.

Both client APIs publish their own OpenAPI 3.1 specification, served by the API itself — an agent can read the contract instead of inferring it from examples.
The Recorder widget's configuration is described by a JSON Schema shipped inside the package, which is what makes the configuration completable and validatable automatically, without guessing a field name.
This documentation is server-rendered: every page reads without executing JavaScript, which makes it accessible to any tool that fetches it.

text

GET /api/v3/docs/openapi.v3.1.yaml
GET /v2.1/docs/openapi.v3.1.yaml

What's planned

Three more pieces are planned. None of them is available yet — treat every item below as a direction, not a capability to reach for today.

A machine-readable index of this documentation, planned, with a Markdown twin next to every page.
Downloadable skills, versioned, planned, for a team to drop into its own project.
An integration MCP server, planned — described in full below.

The integration MCP server

Its reason for existing is singular: while an agent is writing integration code, it needs to check what it just did — was the container actually created, did the message actually reach released, what did the API actually record. It is a verification tool, not an execution tool.

Guarantees
Guarantee	What it means
Environment	Test environment only — no action ever reaches production.
Access	Issued and revoked from the customer portal, tied to a platform, time-limited.
Read by default	Container state, list of containers, message state and content, a container's links — plus creating test containers.
Out of scope by default	notify and unlock — the two operations that reach a real recipient.
Logging	Every call is logged like an API call and stays visible in the portal.

Working with an agent today

Until the MCP server ships, the most useful thing a team can do is hand its agent the sources this page already named — both OpenAPI specifications, plus the three pages below.

Recorder configuration: The JSON Schema that makes the widget's configuration completable and validatable automatically.
Containers and messages: The container/message split an agent guessing on its own gets wrong most often.
Identifiers: The crid/urid/editKey distinction that the same guessing gets wrong just as often.