# Installing it, manually

> One URL, no API keys. You'll sign in through a normal browser window, exactly like logging into Revo.

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

### What you need

- A Revo account with an active workspace membership.
- An MCP-capable client (see below).
- Nothing else. There is no token to generate, no secret to paste, no config file to hand-edit unless your client requires one.

### The address

- **Server endpoint**: `https://api.revo.ai/mcp`

> **Don't use**
>
> `https://www.revo.ai/mcp` is not the server. The endpoint lives on the API host, not the marketing site.

### Claude, desktop and web

1. Open **Settings → Connectors**.
2. Choose **Add custom connector**.
3. Name it `Revo` and paste `https://api.revo.ai/mcp` as the URL.
4. Click **Connect**. A browser window opens on Revo's sign-in page.
5. Sign in and approve the connection.

The connector then shows as connected, and Revo's tools appear in the tool list. Leave the “Advanced settings” (client ID and secret) empty, because the server registers your client automatically.

### Claude Code

```
claude mcp add --transport http revo https://api.revo.ai/mcp
```

Then run `/mcp` inside Claude Code and pick **Authenticate**. Your browser opens, you sign in, and you're done. Add `--scope user` to make it available in every project rather than just the current one.

### Cursor

Add this to `~/.cursor/mcp.json` for all projects, or `.cursor/mcp.json` inside one project:

```json
{
  "mcpServers": {
    "revo": {
      "url": "https://api.revo.ai/mcp"
    }
  }
}
```

Cursor will prompt you to sign in the first time it connects.

### VS Code (GitHub Copilot)

Add to `.vscode/mcp.json` in your workspace:

```json
{
  "servers": {
    "revo": {
      "type": "http",
      "url": "https://api.revo.ai/mcp"
    }
  }
}
```

### Any other client

Most MCP clients accept the same shape. The three facts a client needs:

| Setting | Value |
| --- | --- |
| URL | `https://api.revo.ai/mcp` |
| Transport | Streamable HTTP (not SSE, not stdio) |
| Authentication | OAuth 2.1, discovered automatically |

If your client asks for an API key or a bearer token, it is misconfigured for this server. Revo issues none, and a manually pasted header will be rejected.

### Checking it worked

Ask your assistant something only Revo would know, such as “list my open action items” or “find my meetings from last week”. If tools are wired up correctly it will call `list_action_items` or `find_meetings` and answer from real data.

To confirm the server is reachable at all, without signing in:

```
curl https://api.revo.ai/.well-known/oauth-protected-resource/mcp
```

A healthy server returns its resource identifier and the address of the sign-in service:

```json
{
  "resource": "https://api.revo.ai/mcp",
  "authorization_servers": ["https://sso.revo.ai"],
  "bearer_methods_supported": ["header"]
}
```