MCP

The Model Context Protocol surface is not a wrapper bolted on afterwards — it sits behind the same auth, metering and quota chain as the REST routes. An agent calling through MCP is subject to exactly the limits a script would be.

What an agent sees

Each actor appears as a tool, with its input schema derived from the same wire contract that shapes its output. There is no second definition to drift.

Connecting

Point any MCP client at the endpoint with an API key. Claude, Claude Code and Cursor are the ones we test against on every release; anything that speaks the protocol should work.

Scoping

Issue a key scoped to one actor and the MCP surface exposes exactly that tool. It is the cleanest way to give an agent one capability instead of a catalogue.