McpClientRuntimeCapability (platform.mcp.client) exposes McpClientRuntimeApi for consuming existing platform MCP connections. It is independent of Analytics and dashboard plugins. To publish your own server or App, use MCP Tools and Apps.
The current client exposes read-only tools.list/call. Resources, Prompts, Tasks and subscriptions are not exposed by this API.
Discover and call
request.toolName to your application’s approved operation catalog and validate its arguments. Discovery alone does not approve every returned tool for your workflow. In a controlled execution, set operationKey to the host’s stable call identity to prevent replay.
McpClientScope contains the trusted actor’s tenant, organization and user, saved workspaceId/toolsetId/serverName, an AbortSignal and absolute deadlineAt in milliseconds. The host requires the current authenticated identity, workspace access and a matching MCP toolset. URLs, credentials, connection snapshots and policy overrides are not inputs.
Tool policy and results
- Eligible tools are enabled and model-visible, declare
readOnlyHint: true, and do not declaredestructiveHint: trueor require task execution. Read-only hints narrow selection; they neither grant access nor prove remote behavior. contractHashpins schemas and annotations, not remote code or authorization. Changed contracts require rediscovery and explicit caller review.- Arguments and structured output undergo JSON Schema validation without coercion. Interaction requests, tool errors and invalid output fail.
- Results contain optional
structuredContentand plaintextblocks. Accept text JSON only when your application’s contract explicitly permits it. Resource links are not fetched automatically.