Google Reviews MCP connector
The Google Reviews connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent read your Google Reviews for every location, draft and post replies, and keep account and location details current, all inside each person's own access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Google Reviews to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Google Reviews once
-
Open Connections, choose Add connection, and pick Google Reviews.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Google Reviews app, then approve. Google Reviews needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Google Reviews MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Google Reviews MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Google Reviews MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Google Reviews to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Google Reviews through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Catch up on this week's reviews
Ask for every review left across your Google Reviews locations since Monday and get a summary of the ratings, the themes, and the ones that still have no reply.
-
Support
Reply to a review while it is fresh
Pull up a specific review, draft a reply in the company's voice, and post it to Google Reviews without leaving the conversation.
-
Operations
Add a location when a branch opens
Create the new location under the right Google Reviews account and update the details as the opening date and address settle.
-
Customer Success
Spot the unhappy customers first
List the recent one and two star reviews for a location, read what went wrong, and decide who follows up before a reply goes out.
-
Leadership
Compare locations on rating and volume
Fetch the reviews for several Google Reviews locations at once and see which sites are gaining ground and which need attention.
-
Operations
Take down a reply posted by mistake
Find the reply that went out with the wrong tone or the wrong facts and remove it from Google Reviews so a corrected one can replace it.
Try asking
- “Show reviews left on our Manchester location this week.”
- “Draft replies to the three lowest rated reviews.”
- “Which locations under this account have unanswered reviews?”
Compare
Elaichi vs Zapier MCP vs Composio for Google Reviews
All three can connect Google Reviews to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Google Reviews tools | Allow or restrict single Google Reviews tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Google Reviews call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Google Reviews tools for your AI agents
14 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google Reviews, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Google Reviews gets you
6 screens from the product, each doing one job for your Google Reviews account.
The agent
Ask about reviews, get real answers.
Plain language questions read live Google Reviews reviews, locations and accounts.
- reviews
- replies
- locations
- accounts
Ask Elaichi to work across your apps.
Show reviews left on our Manchester location this week.
Draft replies to the three lowest rated reviews.
Which locations under this account have unanswered reviews?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Any MCP client reaches Google Reviews.
Claude, ChatGPT and Cursor connect over OAuth through one org endpoint.
Copy the endpoint
Tool catalog
14 Google Reviews tools, no custom code.
Reviews, replies, locations and accounts are listed with every method ready.
- List all Google Reviews reviews
- Get single Google Reviews review by ID
- Google Reviews reviews create reply
- Google Reviews reviews delete reply
Toolboxes
Each team gets its own toolbox.
Support, marketing and local teams see only the Google Reviews tools they need.
- Support
- Marketing
- Local operations
- Regional managers
Shared connections
Teammates reply without touching a credential.
Every Google Reviews connection shows who linked it and which teams share it.
- Support EMEA
- Marketing
- Retail North
- Retail South
Audit log
Every reply and edit is recorded.
When, who, what happened, type and resource for each Google Reviews call.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, replies ship after approval.
Six steps fetch reviews, group them, draft a digest, then post back.
Google Reviews digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch reviews
Google Reviews
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Google Reviews
Queued
Collections and dashboards
Review numbers computed, not requested.
Four metrics, 14 days of new reviews and a team breakdown, refreshed on schedule.
Google Reviews health
Refreshed 4 minutes ago · every 15 minutes · from the reviews collection
Reviews
1,284 ↓ 12%
Replies
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Reviews created
Last 14 days
By team
Share of activity
Support EMEA 34%
Marketing 27%
Retail North 21%
Retail South 18%
FAQ
Frequently asked questions
How do I connect Google Reviews to Claude?
Connect Google Reviews in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Google Reviews signs in over OAuth, and because Google requires you to register your own OAuth application, one person brings a client ID and secret from Google once when the connection is set up. After that, everyone else just clicks through the Google sign-in screen and never sees those values.
Does Google Reviews work with ChatGPT and Cursor as well as Claude?
Yes. Once Google Reviews is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Google Reviews once and every client picks it up.
What can an AI agent actually do with my Google Reviews data?
Through this connector an agent can read the reviews for any of your Google Reviews locations, pull a single review or a batch of them, and post or remove a reply. It can also list your Google Reviews accounts and locations, add a location, update its details, or remove one. In practice that means asking for this week's reviews, drafting a reply, and posting it, all in plain language.
Does connecting Google Reviews give the AI access to every account and location?
No. A Google Reviews connection runs inside the access of the person who signed in, so the AI sees only the accounts and locations that person can already manage in Google. Elaichi can narrow that further, for example to reading reviews without posting replies, but it can never widen what Google Reviews itself allows that person.
Can I stop an agent from deleting or changing things in Google Reviews?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Google Reviews and posting replies while blocking reply deletion or any change to accounts and locations. A blocked action is never shown to the AI client at all, so no prompt, however worded, can reach it.
What happens to a Google Reviews connection when someone leaves?
Offboarding a person in Elaichi ends their Google Reviews access at once, across Claude, ChatGPT, Cursor, and every other client. If they had shared a Google Reviews connection with a team, it keeps working for everyone else. Disconnecting Google Reviews once in Elaichi removes it from every client in one step.
Does the Google Reviews MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Google Reviews is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Google Reviews?
Yes. Both let Claude, ChatGPT or Cursor use Google Reviews. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Google Reviews call.
How is Elaichi different from Composio for Google Reviews?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Google Reviews: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Google Reviews in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.