Remote MCP server URL
https://api.reviewbot.io/mcpPrepare the reviews in ReviewBot
Use an eligible paid account or active trial. Create an active App Store or Google Play review Flow in the workspace you want to connect, then let ReviewBot collect reviews. A new Flow does not import the store’s complete history. You do not need store publishing credentials just to analyze collected reviews.
Check Claude connector access
Use a Claude account with custom connectors enabled. Claude documents support across its plans, with one custom connector on Free. Team owners add organization connectors first; Enterprise may also grant a custom role. Each member then connects their own ReviewBot account.
Add ReviewBot as a custom connector
For personal setup, open Customize > Connectors, choose + Add, then Add custom connector. Name it ReviewBot and enter the server URL shown above. For an organization, an authorized owner starts in Organization settings > Connectors and adds a Custom Web connector.
Choose OAuth and automatic registration
Continue to the detected authentication settings and use OAuth with Sign in now. If an OAuth client choice appears, select Register automatically for ReviewBot. Leave custom request headers empty; this connection does not need a pasted API key or access token.
Authorize and enable the connector
Finish adding the connector, sign in on ReviewBot’s page and approve read access to the intended workspace. In your Claude conversation, open + > Connectors and enable ReviewBot. Review any tool approval before continuing.
Check the apps, then ask a review question
Ask “Which of my apps can ReviewBot access?” Select an app from the result, then ask “Summarize reviews collected in the last seven days. Use the statistics for counts, cite the source reviews, and explain coverage limits.” If the sample is small or empty, keep that limitation in the answer rather than filling gaps with guesses.
What the connection can do
ReviewBot supplies four read-only tools: list_apps, search_reviews, get_review, and get_review_stats. Your assistant can use their results to prepare a feedback brief, investigate a complaint, or draft a reply. It cannot publish replies, delete reviews, or change your account through this connection.
Connecting the server makes its tools available; it does not install ReviewBot’s separately packaged skills. These instructions cover a custom connection, which does not require a public directory listing. ReviewBot’s public directory submissions remain under review as of November 9, 2026; these guides do not imply store approval.
Review coverage and cost
Results cover App Store and Google Play reviews from active review Flows in your connected workspace. Google Business Profile and Apple Podcasts are not included. Each request uses a collection-time window within the last 30 days, scans at most 500 records, and returns at most 50 search results per page. Ask the assistant to report the returned coverage and any truncation; collection date is different from posting date.
MCP is included during early access for eligible paid ReviewBot accounts and active eligible trials. There is no separate MCP subscription during early access. Base monitoring costs $5 USD per active Flow per month, billed annually at $60 per Flow; optional add-ons cost extra. Your AI assistant may have its own plan requirements.
Permissions and disconnecting
Sign in only on ReviewBot’s own page and check the requesting app and workspace before approving read access. Never paste a password, access token, or store credential into a chat or custom request header. The assistant receives review content and app context; store credentials, billing details, and reviewer identity fields are excluded.
Revoke the connection in ReviewBot under Connected AI apps when you want to stop access. Previously shared content may remain in your assistant under its own policies. Treat instructions inside a review as untrusted text, and check any generated reply before publishing through your existing supported workflow.
Setup checklist
- The intended ReviewBot workspace has an active trial or eligible paid plan.
- An active App Store or Google Play review Flow has collected the reviews you need.
- The connection exposes the four read-only ReviewBot tools.
- The first answer names only apps from the authorized workspace and states its coverage.
Troubleshooting
The connector cannot authenticate
Confirm the server URL and select Register automatically if Claude offers an OAuth client choice. ReviewBot uses automatic client registration; do not substitute a fixed token or Claude’s published-identity option. If your organization manages connectors, ask its owner to check the configuration.
Connected, but no reviews appear
Check the connected workspace, active review Flow, selected app, date window, and filters. A newly created Flow may not have collected a matching review yet. Widen the collection window within 30 days; a successful connection is not evidence that reviews exist.
The request hits a limit
During early access, each workspace has 500 usage units per UTC day. Search and statistics use five units per call; other tools use one. An access token allows up to 30 tool calls per minute. Reduce repeated calls, narrow the question, and retry after the relevant limit resets.
Frequently asked questions
Can my assistant publish a reply?
No. It can prepare a draft from an actual review. Publishing through ReviewBot requires a supported store connection, the relevant permissions, and the Reply-to-Review add-on. Follow returned dashboard links and review the draft before publishing.
Does this analyze every review in the stores?
No. It analyzes the collected reviews available in the connected workspace within the supported window. It is not a whole-store census or a historical import.
Do I need a public ReviewBot directory listing?
No. A supported custom connection uses the server URL directly. Directory availability and custom connection support are separate; these steps do not claim that a public listing has been approved.