MCP status

The source generates descriptions of registered API operations and scopes. It does not currently provide a deployed MCP transport or a supported command for starting one.

Use HTTP today

Follow the read-only quickstart. An API token and a recognized owned result establish a useful integration path without requiring an assistant transport.

The endpoint catalog shows registered methods and permissions. The generated manifest mirrors that boundary; it is not a second set of unlimited actions.

What is planned

Connections to additional assistant and automation tools appear on the public roadmap. No vendor availability, connection URL or delivery date is promised.

Do not advertise an unsupported launch command or interpret a manifest file as a running server.

Requirements for a future transport

A future interface needs verified admitted-user identity, owned record checks, least-privilege scopes and explicit user intent for financial writes. It must retain idempotency and import-consent rules, unavailable states and safe diagnostics.

Server-side tool execution must not expose service-role credentials to the client or create an alternative ledger write path. See generation drift for how a machine description stays tied to actual behavior.