MCP server
The buyer-facing MCP server — auth-gated and entitlement-scoped.
@caisson/mcp-server is the buyer-facing MCP server your AI agent connects to — to drive
generation, configuration, and the metered operations the base exposes. It is a first-class surface,
not a side door.
The contract
Every tool call is auth-gated with the same EdDSA-JWT issued by @caisson/auth,
and entitlement-scoped: an agent can only reach the tools the buyer's entitlements cover. A token
without an entitlement does not see the tool — scoping happens before dispatch, not inside it.
// .mcp.json — the agent connects with the buyer's token.
{
"mcpServers": {
"caisson": {
"url": "https://mcp.example.com",
"headers": { "Authorization": "Bearer ${CAISSON_TOKEN}" },
},
},
}A call outside the token's entitlements is refused, not silently downgraded:
$ caisson-agent call generate.edition --edition compliance
ERROR entitlement_required: token is not scoped for "compliance"Related
Auth
Issues the EdDSA-JWT every tool call verifies.
AI config
Agent-assisted setup runs through these tools.
This page covers the essentials. The full @caisson/mcp-server API reference
— the tool catalog, the entitlement model, and the generation flow — is still
expanding.