Set the current user's API key for an api_key MCP server
Stores the user’s own API key for an enabled api_key server in one of their knowledge stores (encrypted at rest) and pushes it to their vault. Credentials are per-user; there is no shared store-level key.
Authorizations
Use Authorization: Bearer
Response
The updated connection
A user's credential for one external MCP server URL (account-scoped, no secrets exposed). All non-none modes are per-user. A synthesized row (a server the user could connect but hasn't) has a null id and status not_connected.
connected, expired, revoked, error, not_connected Auth mode of the servers using this URL; null for an orphaned connection.
oauth, api_key, none True when this is an api_key connection with a key stored.
Names of the enabled servers (across the user's stores) that use this URL.
False when no enabled server in any of the user's stores still references this URL.