# Connect REVU to your AI assistant

REVU runs a Model Context Protocol (MCP) server, so an AI assistant can answer questions about your
organization from REVU directly: "how did my site do this week", "which pages do AI crawlers miss",
"what are reviewers unhappy about this month". The assistant reads; it never changes anything in
REVU.

```text
https://mcp.revu.ai/mcp
```

## Connect

You need the URL and your REVU sign-in. The assistant sends you to REVU to approve the connection,
then back.

| Assistant | How |
| --------- | --- |
| Claude | Add a custom connector with the URL, then sign in to REVU. |
| ChatGPT | Add a custom connector with the URL (developer mode), then sign in to REVU. |
| Cursor | Use the install link in REVU's settings, then sign in. |
| VS Code | Use the install link in REVU's settings, then sign in. |
| Claude Code | `claude mcp add --transport http revu https://mcp.revu.ai/mcp`, then run `/mcp`, choose `revu` and sign in. |
| Any MCP client | Add a remote server (streamable HTTP) with the URL. |

When you approve, you choose which of your organizations the assistant can read. The connection
acts as you: it reads what you can read in REVU, no more. You can see and disconnect your
assistants in REVU at any time, and a connection ends by itself if you leave the organization or
sign out everywhere.

The server speaks MCP `2026-07-28` and the earlier revisions, and keeps no session, so a
connection survives REVU deploys.

## What an assistant can ask

The tools follow your organization's products. Every answer states what it covers: the period
(after your plan's history limit), timezone, environment, website or app, and which traffic. Ask
your assistant to quote that scope with the numbers.

| Tool | Answers |
| ---- | ------- |
| `account_overview` | Your organization, plan, products, websites and apps, and example questions. A good first call. |
| `behavior_overview` | A site's headline numbers against the previous period: visitors, engagement, sessions, top pages, sources, countries, devices, bots and AI agents. |
| `behavior_trends` | One event or audience over time, or by hour of day or day of week, optionally split by page, country, device, browser, source, channel or an event property. |
| `behavior_funnel` | Conversion through 2 to 8 steps, and where visitors drop off. |
| `behavior_explain_change` | Why a number moved: what changed by channel, source, page, country, device and browser against the period before. |
| `behavior_pages` | Every page with views, visitors, engagement time, scroll depth, exit rate and rage clicks, sorted the way you ask. |
| `behavior_features` | Which buttons, links and forms people click, and which ones they rage click, by page. |
| `behavior_events` | Which events a site records, with counts. Search by name and page through them. |
| `behavior_event_properties` | What one event carries: its properties and their most common values. |
| `behavior_paths` | Where visits go after a page or event, or what led to it, and where they end. |
| `behavior_sources` | Where visitors come from (channels, AI answer engines, campaigns, referring sites) and which sources convert. |
| `behavior_retention` | Whether visitors come back, by day, week or month. |
| `behavior_crawl_coverage` | Which search and AI crawlers read your site, which pages they miss, and which are stale. |
| `behavior_crawler_access` | Whether crawlers can reach your site: what robots.txt allows each one, and, with the Server SDK, which requests your site refused or failed. |
| `behavior_performance` | Core Web Vitals (LCP, INP, CLS) as p50, p75 and p95, rated good, needs improvement or poor, by page or device. |
| `behavior_sessions` | Individual recent visits, with where each came from, when you ask to see them. |
| `behavior_saved` | Your saved cohorts, insights and dashboards. Name a cohort in a question to count only those visitors. |
| `feedback_summary` | Review volume, rating, sentiment and negative share against the previous period, with ratings by version. |
| `feedback_themes` | What reviewers talk about: topics, sentiment and intent, and what is rising. |
| `feedback_reviews` | Individual reviews of your own apps, when you ask to read them. |
| `reports_list`, `report_get` | Your completed REVU intelligence reports. |

Assistants that support prompts also offer ready-made questions: a weekly report, what changed
and why, where crawlers miss your site, review themes this month, and a product pulse that combines
behavior and reviews.

## Insights first

REVU answers with insights: counts, rates, trends, themes and findings. Individual items appear
only when you ask for them, a few at a time.

- **Your own data.** Individual visits and reviews of your own apps are available on request,
  at most 25 per answer.
- **Apps you follow but do not own**, such as competitors' apps: themes and counts only, never
  their review text.
- **Your visitors stay private.** No answer carries a visitor, person, device or IP identifier, or
  a review's author. Emails and phone numbers in quoted text are masked. Counts by page, country,
  device or source are exact, as in REVU. Under a filter on an event property or a saved cohort,
  1 to 4 visitors read "fewer than 5", and a property value sent by fewer than 5 visitors is never
  named. Average and median times are never given for fewer than 5 visitors.

REVU treats an app as yours when its store listing's developer website is a site of yours that
sends REVU events, or is on one of your organization's verified domains.

## Usage

AI assistant requests and individual items have a monthly allowance that depends on your plan.
As your organization nears it, answers say so; once it is used, answers name the date it resets
and how to raise it. REVU's settings show this month's use.

## Scripts and servers

For a script or a server that cannot sign in through a browser, create a read key in REVU's
settings (Professional and Enterprise plans). A read key belongs to your
organization, reads one environment, and never writes.

```http
POST https://api.revu.ai/v1/read/behavior_trends
Authorization: Bearer revu_rk_prod_...
Content-Type: application/json

{ "touchpoint": "example.com", "page": "/pricing", "period": "last_30_days" }
```

`GET https://api.revu.ai/v1/read` lists the tools your key can run, with each one's input and output
JSON Schema. Every MCP tool above is available this way, with the same answers. A read key also
works as a bearer token at the MCP URL, for clients configured by hand.

| Status | Meaning |
| ------ | ------- |
| `401` | No key, or the key is unknown, revoked or expired. |
| `402` | This month's API requests are used. |
| `403` | The plan is not active. |
| `404` | No such tool for your organization. |
| `422` | Invalid input, or a question the tool cannot answer as asked; the message says what to change. |
| `429` | More than 60 calls a minute with this key; wait for `Retry-After`. |