Troubleshooting MCP connections
Work down this list. The causes are genuinely different, and so are the fixes -- several of them are not something you can solve in your workspace settings, and knowing that early saves an afternoon.
1. "Remote MCP is not enabled yet"
What it means: MCP is not available on this Conviro installation at all.
Who can fix it: nobody inside your workspace. This is platform configuration, not a setting.
There is no toggle to look for. The feature is being rolled out gradually, and your Overview page will stop saying this when it reaches your installation.
2. "MCP is not enabled for this workspace"
What it means: MCP exists on this installation, but your workspace has not switched it on.
Who can fix it: a workspace owner or admin, in Settings -> AI & MCP -> MCP -> Advanced.
If you are not an owner or admin, ask one. This one really is a setting.
3. Authorization was refused
What it means: you reached the Conviro consent screen but the connection did not complete.
Check, in order:
- Are you signed in to the right workspace? The consent screen names it -- read that line before approving.
- Does your workspace allow members to connect their own clients? If not, an owner or admin has to make the connection.
- Did you approve the request, or close the window? Closing it cancels the connection.
4. The connection used to work and stopped
Most likely: it was revoked, or it expired.
Open Settings -> AI & MCP -> MCP -> Connections and look at its status. Revoked or Expired both mean the same thing for you: connect again from the start. Reviving a revoked connection is deliberately not possible.
If it still shows Active, the problem is more likely on the assistant's side -- see step 6.
5. A tool is not available to the assistant
What it means: the assistant cannot see an action you expected it to have.
Usually one of:
- the permission was not granted to that connection
- the capability is switched off for your workspace or the platform
- you are asking for something that writes, and writes are not currently available
Check Settings -> AI & MCP -> MCP -> Permissions to see what is actually in use. If it is a write, that is expected today -- Conviro MCP is read-only.
6. Your AI provider does not offer custom connections
What it means: the limitation is on the assistant's side, not Conviro's.
Support for custom MCP connections depends on which plan you have with that provider, and sometimes on your organisation's policy there. On some business and enterprise plans an administrator must enable it before members can add one.
Check your provider's own documentation and settings. Conviro cannot change this for you.
7. Redirect URI mismatch
What it means: the address your assistant returned to did not exactly match the one registered for the connection.
Registered addresses are matched exactly -- that is deliberate and is a security control, not a strictness to be relaxed. A single character, a missing slash or a different subdomain is a mismatch.
Re-run the setup from the start rather than editing the address by hand, and if it persists, contact support with the exact error your assistant showed.
8. Writes are unavailable
This is expected. Conviro MCP is read-only today.
An assistant cannot change settings, edit knowledge, reply to customers, assign conversations, publish or schedule. If you asked for one of those, the refusal is correct behaviour rather than a fault.
Still stuck?
Take a look at Settings -> AI & MCP -> MCP -> Activity first. If your attempts appear there as refusals, the connection is reaching Conviro and the issue is permissions. If nothing appears at all, the assistant is not reaching Conviro, and the cause is in steps 1, 3, 6 or 7.
That single check narrows it down faster than anything else, so it is worth doing before contacting support -- and worth mentioning when you do.