MCP
Availability and contract rules for exposing Clawdbase operations to AI clients.
The planned MCP surface is expected to mirror the six canonical operations. It is not part of the current customer contract and no MCP request should be used in a production workflow today.
Use REST today
Use the authenticated REST API for Agent, Skill, Lineage, Creator, X and Telegram operations. REST provides the live Access Key, idempotency, result and usage-ledger contract.
Sending channel: "mcp" to the operation route returns 501 with code: "mcp_not_available". The request is rejected before reservation or scoring, so it creates no usage charge.
Planned compatibility
When MCP becomes available, Clawdbase will publish its transport URL, supported clients, authentication format and tool reference here. Planned MCP tools will preserve the same six operation names, score meaning and published prices as REST rather than creating a second scoring product.
mcp:invoke is reserved for that future channel. It cannot currently be issued as a usable permission and does not make an Access Key MCP-capable.
What availability will mean
MCP will move out of Planned only after Clawdbase publishes and verifies:
- a public transport and discovery configuration;
- Access Key authentication and operation scopes;
- successful and failed tool calls with correct usage settlement;
- idempotent replay behavior; and
- structured output parity with the REST operation result.
Until those items are published on this page, integrations must treat MCP as unavailable.
Trust boundary
When MCP ships, an AI client should request evidence before a relevant install, delegation or execution decision and apply its own policy. Trust and Confidence will remain evidence, not a code-safety guarantee or permission grant.
Availability gate
No MCP URL or configuration snippet is available. Use the REST API and check Feature status for future changes.