Skip to main content
status: preview Manage organization-owned provider configurations: the OAuth client credentials for your own Link by Stripe or AgentCard application. These identify your application; they aren’t user grants. Wallets created with manage_vault_wallets can reference a configuration by ID or name. You only need this tool to bring your own provider client. KERNEL-managed wallets don’t use a configuration.

Actions

create, update, and delete require an organization-scoped connection. Reads also work on project-scoped connections.

Parameters

provider, client_id, mode, and wallet bindings are immutable. Rotating client_secret affects every wallet bound to the configuration. For Link, publishable_key is required for KERNEL to refresh and revoke imported wallet grants; without it, imported wallets stop working when their access token expires.
client_secret is write-only. Supply it from a trusted client, never by pasting it into chat, and don’t use an MCP client that logs tool arguments. Responses never include it.

Example

Returns the configuration’s ID, name, provider, client_id, timestamps, and, for AgentCard, its test mode.