[shuv1337]

Organization members can list, create, update, and revoke their own scoped MCP connections, and mint and revoke keys on those connections. A member's API key previously received 403 OrganizationForbidden unless that member was an admin.

An Executor app self-call uses the member's managed full-authority key. The host now binds the MCP connection that invoked the call onto that request. Create, update, and mint stay inside that connection's apps, tools, events, and runsAs accounts, so a scoped connection cannot create an all-apps connection or mint a key for a wider connection. A narrowed connection that does not grant every tool of its apps has no manage authority and is refused with 403. A full connection can still create a narrower Mesh-style connection and mint a key on it. runsAs accepts a personal account the member owns; a group-shared account is refused. Another member's connections stay unreachable. Audit lines for connection changes and key mint or revoke include the caller kind and, for a self-call, the calling connection.

mcp-connections.spec.ts
connection-api-keys.spec.ts
connection-keys.spec.ts