Runtime MCP
Runtime MCP exposes a published app as agent tools. Tool names and schemas come from the app’s published DomainConfig.
Connect
Runtime MCP is available per tenant and app:
Calls require a bearer token with the runtime scope, or an app-scoped agent service token issued by the platform. For workspace preview or validation calls, pass workspaceId=<workspace-id> or the X-CES-Workspace-ID header. If both are supplied, they must match.
Do not reuse Design MCP credentials for runtime agents. Design MCP changes app design; Runtime MCP operates the published or workspace-selected runtime.
Generated tools
Runtime MCP generates:
- one command tool per published command
- projection list tools for published projections
- event import and projection rebuild tools for controlled operational use
- channel tools
- user and DM tools
- current-page refresh tools
The exact business tools differ per app. Ask the MCP client to list tools after connecting.
Command tools
Command tools execute business decisions. They validate input, auth, permissions, command logic, and event append behavior through the same runtime pipeline as REST and GraphQL.
Agents should read relevant projections before executing commands. If a command changes user-visible state, explain the action in the channel or user conversation.
Projection tools
Projection tools read current runtime state. Use filters, sorting, pagination, and output controls to keep agent context focused.
Projection output should be treated as read state, not as a source for direct mutation. To change state, execute a command.
Channel and user tools
Runtime MCP includes collaboration tools for channels, entity channels, users, and DMs. Use them to keep agent work visible and tied to business context.
Common flows:
- open an entity channel before discussing a specific case or order
- post an explanation before executing a sensitive command
- set attention when a human needs to respond
- DM a user only when the workflow calls for a private message
Operational tools
Event import and projection rebuild tools are powerful. Limit them to migrations, repair work, and controlled operations. Normal workflows should execute commands.
Agent bridge constraints
Runtime MCP is for published app operation. Do not use it as a substitute for Design MCP. If the app model needs to change, switch to a builder workflow and use a scoped Design MCP workspace.