# 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. Source: https://elaichi.ai/connectors/googlereviews/ ## Facts | | | | --- | --- | | Application | Google Reviews | | Category | Marketing Automation | | AI tools | 14 | | Authentication | Connects over OAuth | | Needs your own OAuth app | Yes | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Google Reviews is connected - 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? ## Connect Google Reviews in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Google Reviews. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Google Reviews tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Google Reviews to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Google Reviews to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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. ## Connect Google Reviews to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Google Reviews to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Google Reviews tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Google Reviews through Elaichi ### Catch up on this week's reviews Marketing. 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. ### Reply to a review while it is fresh Support. Pull up a specific review, draft a reply in the company's voice, and post it to Google Reviews without leaving the conversation. ### Add a location when a branch opens Operations. Create the new location under the right Google Reviews account and update the details as the opening date and address settle. ### Spot the unhappy customers first Customer Success. 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. ### Compare locations on rating and volume Leadership. Fetch the reviews for several Google Reviews locations at once and see which sites are gaining ground and which need attention. ### Take down a reply posted by mistake Operations. 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. ## 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 my team share one Google Reviews connection? Yes. One person connects Google Reviews, brings the client ID and secret once, and shares the connection with a team in Elaichi. Nobody else handles a credential, yet each person still signs in as themselves, so the audit log names who read which review and who posted which reply. ### 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. ## All 14 Google Reviews tools Every tool below is callable through https://api.elaichi.ai/mcp once Google Reviews is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Google Reviews reviews** (List). List Google Business Profile reviews for a specified location. Returns: name, reviewId, reviewer, starRating, comment, createTime, updateTime, reviewReply, reviewMediaItems, reviewReplyUrl. Required: account_id, location_id. Max 50 per page. - **Get single Google Reviews review by ID** (Get). Get a single Google Business Profile review by id. Returns: name, reviewId, reviewer, starRating, comment, createTime, updateTime, reviewReply, reviewMediaItems, reviewReplyUrl. Required: account_id, location_id, id. - **Google Reviews reviews create reply** (Create). Create or update the owner reply to a specific Google Business Profile review. A reply is created if one does not already exist. Returns: comment, updateTime, reviewReplyState, policyViolation. Required: account_id, location_id, review_id, comment. - **Google Reviews reviews delete reply** (Delete). Delete the reply to a specific Google Business Profile review permanently. The location must be verified for this operation to succeed. Returns an empty 204 response on success. Required: account_id, location_id, review_id. - **Google Reviews reviews bulk get** (Get). Batch retrieve reviews across up to 50 verified Google Business Profile locations in a single request. Returns location review records with name (location resource name) and a full review object including reviewId, starRating, comment, reviewer, reviewReply, reviewMediaItems, and reviewReplyUrl. Required: account_id, locationNames. - **List all Google Reviews accounts** (List). List Google Business Profile accounts accessible to the authenticated user. Returns: name, accountName, type, role, verificationState, vettedState, permissionLevel. No required parameters. The numeric part of `name` is the account_id used by locations and reviews. - **Get single Google Reviews account by ID** (Get). Get a single Google Business Profile account by account id. Returns: name, accountName, type, role, verificationState, vettedState, permissionLevel. Required: id. - **Create a Google Reviews account** (Create). Create a Google Business Profile location group or organization account. Returns the created account: name, accountName, type, role, verificationState, vettedState. Required in body: accountName, type. Organization accounts also require primaryOwner. - **Update a Google Reviews account by ID** (Update). Update a Google Business Profile account. Returns the updated account. Required: id and update_mask. Only accountName is updatable. - **List all Google Reviews locations** (List). List business locations under a Google Business Profile account. Returns: name, title, storeCode, storefrontAddress, phoneNumbers, categories, websiteUri, regularHours, latlng, openInfo, metadata, languageCode. Required: account_id. Optional: read_mask. Max 100 per page. - **Get single Google Reviews location by ID** (Get). Get a single Google Business Profile location by location id. Returns: name, title, storeCode, storefrontAddress, phoneNumbers, categories, websiteUri, regularHours, latlng, openInfo, metadata, languageCode. Required: id. Optional: read_mask. - **Create a Google Reviews location** (Create). Create a business location under a Google Business Profile account. Returns the created location. Required: account_id, plus title and categories.primaryCategory in the body. A storefrontAddress or serviceArea is also required. - **Update a Google Reviews location by ID** (Update). Update a Google Business Profile location. Returns the updated location. Required: id and update_mask. Only fields named in update_mask are changed. - **Delete a Google Reviews location by ID** (Delete). Delete a Google Business Profile location. Returns an empty body on success. Required: id. Locations that cannot be deleted via the API must be removed through the Business Profile UI.