MCP / Use Vendita
Permissions and actions
Understand what your assistant can read, change, and confirm.
Your MCP connection acts as your Vendita user in a workspace. The consent screen shows your account, workspace, and role. MCP does not currently offer a separate read-only permission switch at connection time.
Access by role
| Role | Access through the connection |
|---|---|
| Owner | All role permissions, including billing changes. |
| Admin | All role permissions except billing changes. |
| Member | Operational reads and edits, with restrictions on billing, number purchases, verification submissions, team changes, webhook changes, CRM writes, and API-key management. |
| Viewer | Read permissions. A tool can still require a write permission even if it only previews an operation. |
Ask your assistant to call whoami for the exact permissions on its current connection. A tool appearing in the tool list does not mean your role can run it. Plan and readiness checks also apply.
Which actions need a preview?
| Action | How it works |
|---|---|
| Launch a campaign | Review launch_campaign_preview, then confirm its proposal with launch_campaign_confirm. Launching can send real SMS. |
| Buy a phone number | Review buy_number_preview, then use buy_number_confirm. Number rental is billed. |
| Add prepaid credit | Review add_credit_preview, then use add_credit_confirm. Confirmation charges the card on file. |
| Buy extra simulation allowance | Review buy_simulations_preview, then use buy_simulations_confirm. This spends workspace credit. |
These proposals expire after 15 minutes. If one expires, request a fresh preview and review the new details.
Agent edits, contact imports, campaign setting changes, and other ordinary writes do not all have this two-step API flow. Your assistant may apply them directly when asked. Enabling automatic credit reload authorises future charges under the chosen threshold, amount, and spend cap; it is not just a one-time purchase.
Disconnect access
Open Settings → Connected apps, choose the app, and select Disconnect. Remove or disable it in your assistant as well.
Disconnecting revokes the app’s grant and refresh access. Already-issued access tokens may remain valid until they expire; do not assume every in-flight request stops immediately. Disconnecting also does not pause a campaign that has already launched.
To stop new campaign sends, pause the campaign separately. Existing conversations can continue after a pause.