Developer release truth
MCP and CLI: bounded interfaces, independent release gates.
This page states what is implemented or under test without turning internal progress into an availability claim. Neither surface has a public install channel or general-access compatibility promise today.
Remote MCP
Customer tool contract v1
The contract is deliberately small. It can read scoped operating context and create a draft for human review. It cannot publish, schedule, approve, manage credentials, export tenant data, delete records, or call operator tools.
list_brandsReadTool 1. List only brands visible to the authenticated actor in one workspace.
get_approval_queueReadTool 2. Inspect the actor’s tenant-scoped queue without changing approval state.
get_performance_summaryReadTool 3. Read available measured delivery and performance evidence.
create_draft_from_briefDraftTool 4. Create a reviewable draft through the workspace’s configured AI connection.
Authentication and AI cost
The Open Beta contract uses Authorization Code + S256 PKCE with a 15-minute access token, explicit scopes, and server-resolved identity. It does not request offline access or issue refresh tokens, so the client must repeat interactive authorization after expiry. Draft creation may consume provider usage and is subject to the configured workspace cap; read tools do not.
Direct connector is not a directory listing
After release, a compatible client may connect directly to the verified remote MCP URL. Inclusion in any ChatGPT or Claude directory is a separate third-party review and is not claimed here.
Command line
Thin client, same server policy
The CLI is being built as a client of the same scoped contract, not a second backend or an administrative bypass. Clean-machine installation, login, read, draft, revocation, expiry reauthorization, provenance, and documentation must pass before the label can change. Open Beta credentials are access-only and require browser login again after 15 minutes.
Public install command
Not published — do not install a similarly named package.Support and revocation
No preview connection should outlive the user’s access. The release gate requires immediate server-side revocation and a documented recovery path. Until those controls are live-verified, MCP and CLI stay in development.
Access rule after release: a workspace needs an active paid plan or a confirmed £5 GBP access deposit before MCP or CLI can connect. The preview request and OAuth consent screens never collect payment.
infoqast logout removes local credentials only after the server confirms revocation. Production host compatibility and the public package still require the live gates above.