Updated Oct 2026

Read and reply to Google reviews from Claude or ChatGPT (MCP, step by step)

“Which reviews did we get this week and which ones are still unanswered?” is a question you should be able to ask in plain language. With Prisma’s MCP server you can, from claude.ai, ChatGPT, Claude Code, Cursor or VS Code: the assistant reads your reviews across Google, the App Store, Google Play, Trustpilot, Yelp and 40+ more through the Prisma API, drafts replies, and publishes them only when you say so. This guide is the practical walkthrough; the full reference, with every client’s config, is on Reviews MCP server.

What you need

• A Prisma account (sign up; 2 locations free). A test key or the Test sign-in option returns sample reviews from every platform, so you can try the whole flow before connecting a real account.
• An assistant that supports MCP: claude.ai, ChatGPT (custom connectors, depending on plan), Claude Code, Cursor, VS Code, or Claude Desktop through mcp-remote.

1. Add the connector (two minutes)

claude.ai: Settings → Connectors → Add custom connector → URL https://api.prismareviews.com/mcp. Claude sends you to Prisma to sign in; choose Live or Test and click Allow.

ChatGPT: Settings → Apps & Connectors → Advanced → Developer mode → Create, same URL, same sign-in.

Claude Code: one command, with your key from the dashboard:

claude mcp add --transport http prisma-reviews https://api.prismareviews.com/mcp --header "Authorization: Bearer pk_test_YOUR_KEY"

Cursor, VS Code and Claude Desktop use a small JSON file with the same URL and header; copy it from the docs. The connection shows in your Prisma API keys page as ” (MCP)” and you can revoke it there any time.

2. Connect a platform

Either from the Prisma dashboard (Google sign-in, an App Store Connect key, a Play Console invitation, a Judge.me token, or just the listing URL for Yelp, Tripadvisor and other read-only platforms), or ask the assistant:

“Create a connect link for our Tripadvisor page https://www.tripadvisor.com/Restaurant_Review-… and give it to me.”

The create_connect_link tool returns a link the business owner opens to approve the connection; nothing is connected behind their back.

3. Ask for reviews

Nine tools are exposed (locations, reviews, one review, stats, connections, platforms, connect links, usage, reply); you don’t call them, you ask:

• “List the reviews without a reply from the last 30 days, worst first, with the platform and the link.”
• “Summarise what customers complained about in our App Store reviews this month, grouped by theme, with counts.”
• “What’s our average rating per location this quarter, and which location dropped the most?”
• “Show me every Google review that mentions parking.”

The assistant maps those to list_reviews (filters by location, platform, date and reply status), get_stats and list_locations, and reasons over the JSON. Numbers come from the API, not from the model’s memory.

4. Draft, approve, publish

The rule that keeps this safe: ask for the draft first.

“Draft a reply to Laura’s 2-star review about the slow checkout. Warm, short, no excuses, mention that the second till opens next week. Show it to me before publishing.”

Read it, edit it, then: “Publish it.” The assistant calls reply_to_review with the exact text and Prisma publishes it through the platform’s official API; you get a reply.published webhook (or reply.failed with the platform’s reason) if you’ve registered one. Prisma never writes the text itself and never publishes without a tool call that you triggered.

On platforms with no reply API (Yelp, Tripadvisor, Booking.com, Facebook, G2…) the tool returns reply_not_supported and the link, and the assistant will tell you to answer there.

Honest limits

• Google Business Profile and Trustpilot replies wait on each platform’s approval of Prisma’s access; until then Google reviews are read from the Maps listing (public, read-only). Replies by API work today on the App Store, Google Play, Judge.me, eBay, Trusted Shops, eKomi, WooCommerce, Wix and others (Platforms).
• The assistant can be wrong about reasoning, not about data. Totals and lists come straight from the API; summaries and drafts are the model’s. Check drafts before publishing, every time.
• Public-page platforms are read on a schedule (6 to 24 hours depending on plan), so “this morning’s Tripadvisor review” may not be there yet.
• Cost: each tool call is one API request on your plan, nothing more.

For teams: the same flow in n8n

If you’d rather run it unattended with a human approval step, the n8n node and the Slack alerts workflow do the same with a trigger per new review and an approval queue.

FAQ

Does the AI write and publish replies on its own?

Only if you tell it to. Prisma never writes replies; the assistant drafts them and Prisma publishes exactly the text it receives. Ask for a draft first, approve it, then let it publish.

Which platforms can the assistant reply on?

Those whose official API allows replies and where Prisma’s access is live: App Store, Google Play, Judge.me, eBay, Trusted Shops, eKomi, WooCommerce, Wix and others; Google Business Profile and Trustpilot once each approves Prisma’s access. On read-only platforms the tool returns the link to answer on the platform.

Does it cost extra?

No. Each tool call is one API request on your Prisma plan. The assistant’s own usage is billed by its provider as usual.