update_tribute_connection
Idempotent
Connect a Tribute account to the application or change the connection. Requires manage_settings. Pass at least one field; they are applied in the order apiKey, notificationsConfirmed, paused. Returns the same view as get_tribute_setup. The API key is stored encrypted and no tool returns it. Three things happen in the owner's Tribute account and no tool can do them: creating the API key, creating a digital product and getting it approved by Tribute, and saving the notification link in Tribute (Dashboard → Settings → API Keys → Webhook URL).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| apiKey | No | The owner's Tribute API key, exactly as they gave it. It is checked against Tribute before it is saved. Connects the account, or replaces the key of a connected one (the old key keeps verifying notifications for 24 hours). One key connects to one application only. Never invent one and never repeat it back. | |
| paused | No | true stops offering new checkouts; purchases and refunds already made are still processed. false resumes sales. | |
| applicationId | No | Application (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id. | |
| notificationsConfirmed | No | Records that the owner saved connection.notificationUrl in Tribute. Set it only after the owner says so: nothing checks it, and a wrong "yes" means purchases are paid but never delivered. |