# Limits and known behaviour

> Things that are true by design, so they don't surprise you later.

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

- **One workspace at a time.** There's no picker in the sign-in flow. The connection uses whichever workspace is currently active for your account, and `switch_workspace` changes it globally, including in the Revo web app. The change applies from the next tool call, not the one in flight.
- **Tools only.** The server exposes tools, not MCP prompts or resources.
- **No push notifications.** Because the transport is stateless, the server can't proactively notify your client that something changed. Assistants poll by asking.
- **`ask_revo` is slow by nature.** It bounds itself at 20 tool calls and 15 minutes, and emits progress every five seconds so clients don't give up. A client with an aggressive fixed timeout may still cut it short.
- **No plan execution.** Action item tools manage items; running a plan stays in the Revo app where you approve it.
- **No MCP-specific admin policy.** Connection is self-service and permissions follow your Revo role; there is no workspace switch, per-tool restriction or client allow-list yet. Section 6 is the full inventory.
- **Not in the Claude directory yet.** Manual custom-connector setup is the supported path today, and is functionally identical.