MCP server · included in every plan

The Google reviews MCP server for Claude and Cursor

Connect it once and your assistant reads your live review data and acts on it: which locations have unanswered reviews, how a rating moved this month, who still needs a review request. No dashboard, no export, no Google Cloud project.

Start free trial See the setup

Works during the 14-day trial — $0 today, card required · seven tools · connects in about 3 minutes

› which locations have unanswered reviews this week?

reputemap · list_reviews

Downtown3 unanswered · 1★ 2★ 2★

Riverside1 unanswered · 3★

Uptownall answered

Downtown needs you first — Tuesday's 1★ is still the top review on that profile. Want me to draft replies you can paste in?

› we finished the Henderson job — send them a review request

reputemap · send_review_request

Sent — Henderson gets your review-ask email with the Google link.

Example conversations · demo data — each tab demos different tools of the same server. All seven: list_locations · list_reviews · get_review_stats · draft_reply · publish_reply · send_review_request · get_usage

In short

What the ReputeMap MCP server is

It's a hosted Model Context Protocol endpoint at https://api.reputemap.com/mcp. Any MCP client — Claude Code, Claude Desktop, Cursor, VS Code and the rest — can call it with your ReputeMap API key and work with the Google reviews, locations and rating stats of the business or clients you already manage in ReputeMap.

Because ReputeMap already holds the Google connection, you skip the part that stops most people: no Google Cloud project, no API access application, no OAuth refresh tokens, and no scraping. One command in the tool you already use, and the answers come back in the same window.

A hosted MCP endpoint at api.reputemap.com/mcp — nothing to install, nothing to host.
Seven tools: read your locations, reviews (with the owner replies inlined) and rating stats, draft AI replies, publish an approved reply, send one review request, check credit usage.
Auth is one header: your ReputeMap API key. No Google Cloud project, no API approval queue, no scraping.
Included in every plan and in the 14-day trial. 1,000 billable calls a month, shared with the REST API.
Publishing is explicit-only: publish_reply posts the exact text you approved, is flagged so assistants confirm first, and keeps a manual fallback if Google rejects it.

Why this exists

Reviews don't get ignored on purpose. They get ignored in a tab.

Every tool you buy adds one more dashboard someone has to remember to open. The reviews keep arriving whether or not anybody does.

The alert lands. Then what?

ReputeMap pings you within minutes of a 1★ — that part is solved. Acting on it is what still costs a login, a hunt for the review, and a tab you don't have open at 8:14am. So the reply waits until evening.

The question nobody asks weekly

“How did Downtown actually do this month?” costs a login, three filters and an export — so it gets asked once a quarter, usually after the rating already slipped.

Ten clients, ten dashboards

Agencies don't drop reviews because they stopped caring. They drop them because nobody opens ten dashboards a day, every day, forever.

MCP takes the dashboard out of the loop. The answer shows up in the window you're already working in — your terminal, your editor, your assistant — inside the ten seconds you actually have.

What it can do

Seven tools. Four read, three act.

Small on purpose: everything an assistant needs to answer a real question about your reviews, and exactly one action that touches the outside world.

Tool	What it does	Type	Cost
`list_locations`	Every location the organisation manages, with the ids the other tools take.	read-only	1 credit
`list_reviews`	Google reviews newest-first with the published owner reply inlined. Filter by location, star range, unanswered-only, or the last N days.	read-only	1 credit
`get_review_stats`	Per location and org-wide: review count, average rating, the full 1–5★ breakdown, unanswered count, and activity in a trailing window.	read-only	1 credit
`send_review_request`	Sends one real review-request email through the campaign engine — opt-outs and the suppression list still apply, and a repeat ask for the same customer at the same location isn't re-sent.	sends email	1 credit
`draft_reply`	Reply variants for one review from ReputeMap's tuned generator — the same drafts the app makes. Saves the draft into the app editor; never publishes.	sends email	1 credit
`publish_reply`	Publishes an explicitly approved reply text to the review's Google profile. Flagged destructive so clients confirm first; a Google failure preserves the text with a manual fallback.	sends email	1 credit
`get_usage`	This month's credit usage, so you always know where you stand.	read-only	free

The read tools carry MCP's readOnlyHint; the email tool doesn't — which is the standard signal telling your client to ask before it runs. Each call is one credit against 1,000 a month, shared with the REST API; get_usage is free.

Things to ask

The questions you'd never log in for

These are the ones that quietly go unasked for a quarter. Typed into a chat window, they take four seconds.

Click any prompt to copy it — then paste it into Claude, Cursor, Gemini or whichever assistant you connected.

Managing many businesses? The same question can cross every client at once — see multi-location review management and ReputeMap for agencies.

Copy-paste workflows

Six jobs it does end to end

Each card is one paste-able prompt; the footer line names the tools your assistant will call. Click a card to copy it.

How to connect

Three steps, about three minutes

Create an API key

No account yet? Start the 14-day trial first. Then, in the app: Settings → API keys — owners and admins; the key starts with rmk_ and is shown once.

Start the trial

Add the server

One command, or one config block, in the AI client you already use. Nothing to install or host.

Ask in plain English

Your client picks the right tool and answers from live review data — in the window you already had open.

Claude CodeCursorVS CodeClaude DesktopGemini CLICodex CLIWindsurfAny MCP client

One command in your terminal. (In a hand-written .mcp.json, include "type": "http" — without it Claude Code reads the entry as a local program instead of a web address, and fails.)

bash

claude mcp add --transport http reputemap https://api.reputemap.com/mcp \
  --header "Authorization: Bearer rmk_YOUR_KEY"

~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one.

json

{
  "mcpServers": {
    "reputemap": {
      "url": "https://api.reputemap.com/mcp",
      "headers": { "Authorization": "Bearer rmk_YOUR_KEY" }
    }
  }
}

Copilot agent mode — .vscode/mcp.json in the workspace. The top-level key is "servers", not "mcpServers".

json

{
  "servers": {
    "reputemap": {
      "type": "http",
      "url": "https://api.reputemap.com/mcp",
      "headers": { "Authorization": "Bearer rmk_YOUR_KEY" }
    }
  }
}

Header auth in the connector UI is still an Anthropic beta, so the reliable path today is the local bridge in claude_desktop_config.json (needs Node.js 18+).

json

{
  "mcpServers": {
    "reputemap": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://api.reputemap.com/mcp",
        "--header", "Authorization:${AUTH_HEADER}"
      ],
      "env": { "AUTH_HEADER": "Bearer rmk_YOUR_KEY" }
    }
  }
}

One command — Gemini CLI's mcp add speaks HTTP transport directly.

bash

gemini mcp add --transport http reputemap https://api.reputemap.com/mcp \
  --header "Authorization: Bearer rmk_YOUR_KEY"

~/.codex/config.toml — TOML, not JSON, and the header table is http_headers.

toml

[mcp_servers.reputemap]
url = "https://api.reputemap.com/mcp"
http_headers = { "Authorization" = "Bearer rmk_YOUR_KEY" }

~/.codeium/windsurf/mcp_config.json — note the field is serverUrl, not url.

json

{
  "mcpServers": {
    "reputemap": {
      "serverUrl": "https://api.reputemap.com/mcp",
      "headers": { "Authorization": "Bearer rmk_YOUR_KEY" }
    }
  }
}

It is a standard streamable-HTTP MCP endpoint — point any compliant client at it with one header.

text

URL:        https://api.reputemap.com/mcp
Transport:  streamable HTTP (JSON-RPC 2.0 over POST)
Header:     Authorization: Bearer rmk_YOUR_KEY

Clients that only speak stdio can bridge to it:
npx -y mcp-remote https://api.reputemap.com/mcp --header "Authorization: Bearer rmk_YOUR_KEY"

Then ask: “list my ReputeMap locations” — if the ids come back, you're connected. Full walkthrough and troubleshooting live in the MCP documentation; the REST equivalent is in the developer API docs. Keys are created at Settings → API keys.

Works with

Every MCP client that speaks HTTP

It's a standard remote MCP server, so the list isn't ours to limit. These are the clients whose own documentation confirms a remote streamable-HTTP server with a static Authorization header — each one wants the URL in a slightly different field, so here they are.

Client	Where the config lives	The field it uses
Claude Code	`claude mcp add --transport http`	--header
Cursor	`~/.cursor/mcp.json`	url + headers
VS Code (Copilot agent mode)	`.vscode/mcp.json`	servers → type: http
Claude Desktop	`claude_desktop_config.json`	npx mcp-remote bridge
Windsurf	`~/.codeium/windsurf/mcp_config.json`	serverUrl + headers
Zed	`settings.json → context_servers`	url + headers
Cline	`MCP settings JSON`	type: streamableHttp
Gemini CLI	`gemini mcp add --transport http`	httpUrl + headers
Codex CLI	`~/.codex/config.toml`	url + http_headers
Raycast	`“Install MCP Server” form`	HTTP + headers

Verified against each vendor's own documentation on 5 August 2026. n8n's MCP Client Tool node speaks streamable HTTP with a Bearer credential in recent versions. ChatGPT connectors accept only OAuth today, so ChatGPT is not supported yet — we'd rather say so than let you find out after signing up.

The honest comparison

Three ways to get Google reviews into an AI assistant

Most “Google reviews MCP” results are DIY repos or scrapers. Here's what each route actually costs you before the first answer arrives.

Weeks, if approved

Build your own on the Google Business Profile API

A Google Cloud project, an access application, OAuth plumbing and a server to host. Google's own prerequisites require an email that owns the profile and a Business Profile “verified and active for 60+ days”.

Until the application is approved the API is simply switched off for you: the project sits at 0 QPM (queries per minute), and Google states plainly that 0 QPM means “your project has not yet been approved”. Approved projects get 300.

Fragile and off-limits

A scraper-based MCP server

Reads whatever is public on the page. No owner-reply state, no review-request sending, and it breaks whenever the markup moves.

It is scraping. We don't do it, and we don't recommend building a client business on it.

About 3 minutes

A hosted platform's MCP server

The approval, the OAuth refresh tokens and the sync are already somebody's job. You point a client at a URL and send a key.

You trade that work for a subscription — ReputeMap starts at $29/month with the MCP server included, trial included.

Take the three-minute route

Quota and eligibility wording above is Google's own, from the Business Profile APIs prerequisites (read 5 August 2026). ReputeMap is an independent tool and is not affiliated with Google.

Guardrails

An eager assistant still can't do damage

Your data only

The key reaches exactly what your organisation already owns — your locations, your reviews, your stats. Nothing else is exposed, and cross-origin browser calls are rejected outright.

Publishing needs your explicit yes

publish_reply posts only the exact text you approved in the conversation — it is flagged so assistants ask before running it, every publish is audit-logged, and if Google rejects it your text is preserved in ReputeMap with a manual fallback. Nothing publishes as a side effect.

Opt-outs still win

The one email-sending tool runs through the same suppression and opt-out checks as in-app campaigns, and every send is recorded on that location's campaign, so there's a trail. Asking twice for the same customer at the same location won't send a second email. It is still a real email to a real person, so clients are told to confirm first.

Revoke in one click

Keys are stored only as hashes and shown once. Revoking one cuts access off immediately, and both creation and revocation are written to the audit log.

Technical details

Specifications

Endpoint: https://api.reputemap.com/mcp
Transport: Streamable HTTP · JSON-RPC 2.0 · stateless POST
Auth: Authorization: Bearer rmk_… (X-API-Key also accepted)
MCP revisions: 2024-11-05 · 2025-03-26 · 2025-06-18 · 2025-11-25
Tools: 5 — four read-only, one that sends an email
Credits: 1,000 billable calls/month, shared with the REST API
Rate limit: 60 requests/minute per organisation
Registry: Published as com.reputemap/reputemap

Tool discovery is open — any MCP directory can read the catalogue without a key. Every call that touches review data needs yours.

Straight answer

When it's the wrong tool

You haven't connected a Google Business Profile yet — there'd be nothing to read.
You need Yelp, Facebook or TripAdvisor. ReputeMap is Google-only by design.
You want per-user OAuth rather than one organisation-level key.
You want the assistant to publish replies to Google unsupervised. That's deliberately not on offer.
You haven't started a plan or the trial yet — API keys need an active subscription, and the 14-day trial counts as one.

Everything else about the product — the inbox, alerts, requests and reports the MCP tools read from — is on the review management software page.

MCP server FAQ

What is an MCP server, in plain English?

MCP (Model Context Protocol) is the open standard AI assistants use to reach outside tools. The server is the bridge: connect ReputeMap's once and your assistant answers from your real Google review data instead of guessing. You write no code — you paste one config line and start asking questions.

Do I need a Google Cloud project or API approval?

No. That is the whole point of using a hosted server. ReputeMap already holds the Google connection, so you authenticate to ReputeMap with your own API key and skip the Cloud project, the access application and the OAuth plumbing entirely.

Does the ReputeMap MCP server cost extra?

No. It's included in every plan and it works during the 14-day trial. MCP calls share the same allowance as the REST API — 1,000 billable calls a month, the same on every plan — and the get_usage tool is free and tells you what you've used.

Which AI apps can connect to it?

Any MCP client that supports remote HTTP servers with a custom Authorization header: Claude Code, Cursor, VS Code, Windsurf, Zed, Cline, Gemini CLI, Codex CLI and Raycast all do, and Claude Desktop connects through the mcp-remote bridge. ChatGPT's connector platform only accepts OAuth today, so it is not supported yet.

Can the AI publish replies to Google on its own?

No, and that's deliberate. The server exposes four read tools plus exactly one action: sending a review-request email. Your assistant can draft reply text in its answer, but publishing to Google stays inside ReputeMap where a human approves it.

Is it safe to give an AI assistant an API key?

The key only reaches data your organisation already owns, and the one write tool honours your opt-out and suppression lists, so a customer who unsubscribed will not be emailed. Keys are shown once, stored only as a hash, and revoking one cuts off access instantly.

Point your assistant at your own reviews

Start the 14-day trial, create a key, paste one line — then ask what your reviews did this week. Plans from $29/month, MCP server included.

Start free trial

14-day free trial · $0 today · cancel in one click

The Google reviews MCP server for Claude and Cursor

What the ReputeMap MCP server is

Reviews don't get ignored on purpose. They get ignored in a tab.

The alert lands. Then what?

The question nobody asks weekly

Ten clients, ten dashboards

Seven tools. Four read, three act.

The questions you'd never log in for

Six jobs it does end to end

Monday-morning triage

The client digest (agencies)

Job done → review ask

Complaint themes before they cost you

The rating-drop investigation

Month-end usage check

Three steps, about three minutes

Create an API key

Add the server

Ask in plain English

Every MCP client that speaks HTTP

Three ways to get Google reviews into an AI assistant

Build your own on the Google Business Profile API

A scraper-based MCP server

A hosted platform's MCP server

An eager assistant still can't do damage

Your data only

Publishing needs your explicit yes

Opt-outs still win

Revoke in one click

Specifications

When it's the wrong tool

MCP server FAQ

Point your assistant at your own reviews