ReviewBot MCP · Early access
Connect the App Store and Google Play reviews your team collects to your AI assistant. Find recurring complaints, prepare a feedback brief, and draft replies with the review in context.
14-day trial · No credit card required
Included during early access for eligible paid or trial accounts. Use an assistant that supports remote MCP and OAuth.
“What are people saying about sign-in? Draft a reply I can review.”
“Since updating, sign-in gets stuck.”
“I have to close the app before I can sign in.”
Reply draft
Thanks for flagging the sign-in issue. Could you share your app version and device?
Your team reviews the draft before publishing.
Start with a useful question
ReviewBot provides the reviews and statistics. Your assistant helps turn that context into a brief, an investigation, or a draft you can check.
Bring ratings, recurring themes, and supporting reviews into the same conversation. Ask your assistant to explain what the collected sample covers.
Try asking
“Summarize the reviews collected for my app in the last seven days. Use the review statistics for counts, cite the reviews behind each theme, and explain any gaps in coverage.”
Find reviews about sign-in, billing, or another issue. Narrow the search by app, rating, locale, or a reported app version.
Try asking
“Find recent one- and two-star reviews about sign-in. Show the source reviews, separate reported versions from unknown versions, and list questions for our product team.”
Give your assistant the actual review before it writes. Check the draft, then use your existing reply workflow to publish it.
Try asking
“Draft a helpful reply to this review. Acknowledge the issue and ask only for useful details. Do not promise a fix or release date, or claim anyone has acted unless I confirm it. Leave the draft for me to approve.”
Connect your assistant
Sign in to an eligible ReviewBot account or start a trial. Create an App Store or Google Play review Flow and let ReviewBot collect your reviews.
Set up your first FlowOpen your assistant’s remote MCP connection settings and add this URL. Your assistant’s plan and workspace permissions determine whether custom connections are available.
Streamable HTTP · OAuth with PKCE
Sign in to ReviewBot, check the requesting app and workspace, and allow read access. Start by asking “Which of my apps can ReviewBot access?” Then choose an app for your first review question.
Read the connection guideA custom connection adds the tools; packaged skills are installed separately. After selecting a review, use this prompt and check the draft before publishing.
Your ReviewBot password stays in ReviewBot’s sign-in flow. Never paste passwords, access tokens, or store credentials into an AI conversation.
Know what your answer covers
ReviewBot returns source links, collection dates, and coverage information with the review data. Ask your assistant to cite that evidence and call out gaps.
Access stays tied to the authorizing user and workspace. Your assistant receives review content and app context, without store credentials, billing details, or reviewer identity fields.
Disconnect from Connected AI apps at any time. Review content already shared remains subject to your assistant’s own policies.
App Store and Google Play reviews collected by ReviewBot for apps monitored by active review Flows in the connected workspace. This MCP integration does not include Google Business Profile or Apple Podcasts. It does not import an app’s complete store history.
Use a client that supports remote MCP over Streamable HTTP and OAuth, such as a compatible custom-connector setup. Availability depends on the assistant’s plan and your workspace permissions. Connect using the server URL in the setup section; a public app-directory listing is not required for a supported custom connection.
MCP is included during early access for eligible paid ReviewBot accounts and active eligible trials. There is no separate MCP subscription during early access. Your usual ReviewBot Flow pricing and any reply add-on requirements still apply. Your AI assistant may have its own plan requirements.
No. The four MCP tools are read-only. An assistant can use the returned reviews to prepare a draft, but a person must review and publish it through an existing supported reply workflow. Publishing through ReviewBot requires the appropriate store connection, permissions, and Reply-to-Review add-on.
Each search or statistics request covers a window within the last 30 days, based on when ReviewBot collected the review. Up to 500 records are scanned per request; search returns up to 50 reviews per page. Results report coverage and truncation. These are collected-review samples, not whole-store totals, and collection time is different from the date a reviewer posted.
Each workspace has 500 usage units per UTC day. Search and statistics use five units per call; the other tools use one. Each access token allows up to 30 tool calls per minute. The setup guide documents these limits.
The connected assistant receives the review content and app context needed for your requests. Store credentials, billing details, private integration settings, and reviewer identity fields are excluded. Revoke access from Connected AI apps in ReviewBot. Data already shared may remain in your assistant under its own policies.
Check that the connected workspace has an active App Store or Google Play review Flow and has collected reviews during your selected window. A new Flow does not backfill the entire review history. Try a wider window within 30 days or remove a restrictive filter.
Put your next review to work
Try ReviewBot with your team’s App Store or Google Play reviews. MCP access is included during early access for eligible accounts.