# Questions

> The things people ask before they connect it.

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

#### Does connecting this give Claude access to everything in Revo?

It gives Claude access to exactly what *you* have access to, through the tools listed in section 3. Not your colleagues' private meetings, not other workspaces, not anything your role doesn't permit.

#### Can it delete my data?

No. The user-facing tools create, update, dismiss, snooze and restore. There is no destructive delete among them.

#### Do I need an admin to set this up?

No. Any workspace member can connect it for themselves. Nothing is provisioned centrally, and one person's connection has no effect on anyone else's.

#### Can my whole team share one connection?

No, and that's deliberate. Each person connects with their own account so every action is attributed to them and bounded by their own permissions.

#### How do I disconnect?

Remove the connector in your AI client. That stops it calling Revo, and for an ordinary disconnect it's enough.

If you need access genuinely cut off, a lost laptop or a departing colleague, removing the connector isn't sufficient, because the token lives with the client. Remove the person's workspace membership. Revo checks it on every request, so their next call fails no matter what credentials they still hold. There is no self-service way to revoke an MCP connection on its own today; ask Revo support if you need the underlying grant torn down as well.

#### Does it cost anything?

Some tools consume your workspace's AI usage, the same as using Revo in the app. It isn't a clean split between reads and writes: searching is often AI-backed, and two tools do their work after they've replied. Run `get_my_usage` to see where you stand.

| Cost | Tools |
| --- | --- |
| **Substantial** (agent run) | `ask_revo` is a full agent run with up to 20 tool calls. By a wide margin the most expensive thing here, and the only one worth thinking about before you call it. |
| **Small** (semantic search) | `find_meetings` when you pass a title search, and `search_brain` where the knowledge graph is enabled. Both embed your query to search by meaning rather than exact words. Filtering meetings only by participant or date skips this entirely, and `search_brain` costs nothing on a workspace where the graph is still switched off. |
| **Deferred** (after the call) | `add_document` and `push_conversation` return straight away, then Revo indexes the content and folds it into your knowledge base in the background. The usage shows up shortly after the call rather than during it. |
| **None** (database only) | Transcript reads, every action item tool, memories, usage and workspace tools. Creating an action item does not start planning, that stays on-demand in the app. |

#### Will it appear in the Claude directory?

That's the intention. Until then, the manual custom-connector setup in section 2 is the supported path, and nothing about it is second-class. A directory listing would change discovery, not capability or security.