Connections and OAuthComing soon

A plugin that saves drafts in a CMS or posts to LinkedIn needs an account to do it with. Declare it as a connection setting:

settings:
  - key: linkedin
    type: connection
    provider: oauth2
    scopes: [w_member_social]
  - key: sanity
    type: connection
    provider: mcp

provider says how the account is connected: oauth2 signs in with the service, and mcp uses an MCP server from the team's Connections page. With plugins on, Connections is its own page in the dashboard, listing every MCP server the team has connected and its status.

Installing grants nothingCopy Anchor Link

Installing a plugin never gives it access to anything. The team connects each account separately, and a plugin can only use the tools its manifest grants on that connection: an MCP connection exposes only the tool names in the plugin's allow list.

Tokens stay out of the modelCopy Anchor Link

Connection tokens are sealed like other secrets, added to a request after the model has chosen the call, and never shown to a model or sent back to the dashboard.

ScopesCopy Anchor Link

List the narrowest OAuth scopes the plugin needs. A new version that asks for a new scope or a new connection waits for an admin.