Integrations and access
Understand and revoke MCP permissions
An MCP connection receives specific permissions in one workspace. OAuth grants act as the member who approved them; API keys act as their creator. Scopes limit which tools can run, while workspace and actor checks still apply.
Reviewed October 2026
Choose scopes by task
| Scope | What it allows |
|---|---|
| crm:read | Query CRM records, fetch a record, and read pipeline snapshots. |
| crm:write | Create or update contacts, accounts, and opportunities; add notes. |
| tasks:read / tasks:write | Read tasks, or create and update tasks with write permission. |
| meetings:read | Read meetings organized by the actor, including available notes and transcripts. |
| knowledge:read | Search and read published Knowledge Base articles. |
| search:read | Find passages in workspace content the actor can access. |
Review connected assistants
For a narrower set of OAuth permissions, revoke the old connection and approve a new one with the intended scopes. For an API-key integration, replace the key with a suitably scoped key.
- Open the Connected assistants list in Vesso’s MCP/API settings.
- Check the client, approving member, workspace, granted scopes, and connection activity before deciding whether it is still needed.
- Members can inspect and revoke their own OAuth connections. Workspace administrators can inspect and revoke connections across the workspace.
Understand the audit trail
MCP tool calls record the tool name, acting member, credential context, scopes, and a redacted argument summary, with request metadata such as IP address and user agent. OAuth approval, denial, client registration, and revocation also create audit events.
Free-text payloads are not copied into MCP argument summaries. Audit access follows the workspace’s audit-log entitlement and permissions. Use the acting member and tool name to investigate a change.
Revoke a connection
- Find the assistant in the Connected assistants list and choose Disconnect, then confirm.
- Remove or disconnect the Vesso connector in the AI client so it stops attempting calls.
- For a bearer-key connection, revoke the underlying key in API Access. Removing a client configuration alone does not invalidate that key.
- Test that the old credential no longer works. If access is still needed, create a fresh connection with the intended scope.