Remote MCP / read-only customer plane
Zenith exposes one JSON-RPC MCP endpoint for supported remote clients that can present an organization-scoped bearer token. Every call is authorized against eight generic read-only tool categories.
Eight generic tool categories share one call-time authorization boundary.
Connection sequence
A display-once MCP token does not bypass customer entitlement, source policy, call balance, rate limit, or operation authorization.
Client-neutral contract
Clients connect to the same endpoint with a bearer token. No client receives a policy exception, and no OAuth metadata or client-specific redirect flow is claimed.
MCP Dock / client-neutral
Supported bearer-token MCP clients follow the same authorization and policy decisions.
Create a display-once MCP token
Connect a supported client to the JSON-RPC endpoint
Resolve customer entitlement at call time
Invoke one read-only tool category
Return attribution and weighted-call context
Revoke the token when required
Eight read-only categories
Generic categories communicate public breadth without exposing private tool names, client IDs, or security internals.
Call-time customer authorization · read-only
Call-time customer authorization · read-only
Call-time customer authorization · read-only
Call-time customer authorization · read-only
Call-time customer authorization · read-only
Call-time customer authorization · read-only
Call-time customer authorization · read-only
Call-time customer authorization · read-only
Resilient state contract
Bring attributable source access into AI workflows. retains truthful context, navigation, and a safe next action when live records are empty or unavailable.
Heading, explanation, and recovery path remain.
Text status and stable geometry prevent surprise.
Unavailable data is labeled with an alternate path.
Plain language, stable navigation, and safe recovery.