Viewing or managing an MCP server no longer lets a member call its tools. Connecting now always requires its own
mcp:connect grant, direct or through a role, described below. More on this in Roles and permissions.
Breaking changes
mcp:readandmcp:writeno longer implymcp:connect#8553 - Connecting to an MCP server and calling its tools now always needs an explicitmcp:connectgrant, direct or through a role. Before, a role that could view or manage a server could also call its tools, whether or not that was intended. Existing grants were backfilled with a matchingmcp:connectfirst, so no one loses access they already had; a block on a server still withdraws it, and a direct grant naming the server still outranks a block inherited from a role or from everyone. (Author: @tgmendes)
Bug fixes
- A member's access listing no longer shows a skill they're blocked from reading #8802 - Holding permission to edit a skill no longer makes a read block on that skill disappear from a member's access listing. The listing now hides a blocked skill there, matching how it already behaved everywhere else. (Author: @tgmendes)
