{"version":"2.1.281","anchor":"mcp-read-resource-added-to-the-client-command-control-reques","canonical_anchor":"mcp-read-resource-added-to-the-client-command-control-reques","heading":"mcp_read_resource added to the client-command control request union","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/mcp-read-resource-added-to-the-client-command-control-reques","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### mcp_read_resource added to the client-command control request union\n\nSDK clients can now send an `mcp_read_resource` control request, limited to `ui:\/\/` addresses\n\n**What**\n\nThe SDK is the kit developers use to drive Claude Code from their own programs. It defines control requests, the commands a client can send to steer a session. That list now includes `mcp_read_resource`, which reads a resource from an MCP server, an external tool Claude Code connects to. It only accepts addresses beginning with `ui:\/\/`. Any other address is refused.\n\n**Why**\n\nPrograms built on the SDK can fetch interface resources from MCP servers directly. The `ui:\/\/` limit keeps other kinds of resource out of reach through this request."}