# Troubleshooting

> Almost every failure is one of four things.

Product: Revo MCP Server. Source: https://www.revo.ai/docs/mcp/troubleshooting

| What you see | What to do |
| --- | --- |
| **“Couldn't register” or the connector won't add** | Check the URL is exactly `https://api.revo.ai/mcp`, with the `api.` host, no trailing slash, no path after `/mcp`. Leave the advanced client ID and secret fields empty. |
| **It connects, but there are no tools** | Your account resolved but holds no permissions, usually a workspace membership that was removed, or a sign-in under a different email than the one on your Revo account. Check `list_my_workspaces`; if that's missing too, sign out of the connector and reconnect. |
| **“The knowledge graph isn't enabled for this workspace yet”** | Expected. The knowledge graph is in early access, and `search_brain` stays listed even where it's switched off, so your assistant may try it and get this note back. Everything else works normally. Access is open on request: ask your Revo contact to enable it. |
| **Some tools are missing** | Expected. You're seeing exactly the tools your role permits. Per-teammate usage needs workspace Admin; `revo_admin` tools are Revo staff only. |
| **Suddenly unauthorized mid-session** | The token expired and the refresh failed, or your workspace membership changed. Reconnect the connector. |
| **Results are from the wrong workspace** | Call `list_my_workspaces` to see which is active, then `switch_workspace`. Remember the switch applies from the following call. |
| **`ask_revo` times out in the client** | Revo sends keep-alive progress every five seconds; some clients ignore it and enforce a hard limit. Narrow the question, or use the specific tools directly instead. |

#### Confirming the server itself is healthy

```
curl -i -X POST https://api.revo.ai/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'
```

A healthy server answers `401` with a `WWW-Authenticate` header pointing at its discovery document. That is the correct response to an unauthenticated call: it's how your client learns where to sign in. Anything else (a 403, a 404, a timeout) means you have the wrong address.