Skip to main content

​
What an assistant can never do

Through MCP, an assistant cannot see or change billing, your team, API keys or webhook endpoints; cannot delete conversations; cannot erase or export a person’s data; and cannot change experiment results. It can only act in the one workspace it was connected to. The chat on your website never gets these tools.

​
Disconnect an assistant

Open Integrations → API → AI assistants. Each OAuth connection shows the app’s name, when it was connected and last used, and its access (Full access or View only). Select Disconnect and confirm. It loses access at once; connecting again needs a new sign-in. For Claude Code, Cursor or anything using an API key, revoke that key in API keys. An OAuth connection stays signed in while it is used. One that goes unused for 30 days has to sign in again.

​
Limits

Each tool call counts as one request against the connection’s per-minute rate limit. Tool results are capped at 200,000 characters.

​
Troubleshooting

The connection’s access doesn’t include that tool. A View only connection, the read-only URL, or a key without the scope hides it. Disconnect and connect again with Full access, or create a key with the scope.
Ask an owner or admin of the workspace to connect it, or to change your role in Team.
Consent requests last 15 minutes. Start connecting again from your assistant.
The workspace has to complete its card step in Darwin before any API or MCP access works.