MCP server — Claude & Cursor
Connect Claude Code, Claude Desktop or Cursor to your Google reviews with the ReputeMap MCP server. One command, your API key, zero code.
Talk to your Google reviews from Claude
ReputeMap hosts an MCP server (Model Context Protocol — the open standard AI assistants use to reach external tools). Connect it once, and Claude or Cursor can work with your review data directly:
- “Show me every unanswered review under 3 stars from the last week, worst first.”
- “How did the Downtown location’s rating move this month vs last?”
- “Draft replies to the three newest negative reviews in a calm, non-defensive tone.”
- “We just finished the Hendersons’ job — send them a review request.”
No scripts, no exports, no glue code. Included with every paid plan — and it works during the 14-day trial.
What you need
- A ReputeMap account with an active plan (or trial) — start here.
- An API key from Settings → API keys (looks like
rmk_…, shown once).
The server lives at:
https://api.reputemap.com/mcp
Claude Code
One command:
claude mcp add --transport http reputemap https://api.reputemap.com/mcp \
--header "Authorization: Bearer rmk_YOUR_KEY"
Then just ask: claude "which of my locations has the most unanswered reviews?"
Claude Desktop
Claude Desktop connects through the mcp-remote bridge (needs Node.js installed). Add this to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"reputemap": {
"command": "npx",
"args": [
"-y", "mcp-remote", "https://api.reputemap.com/mcp",
"--header", "Authorization: Bearer rmk_YOUR_KEY"
]
}
}
}
Restart Claude Desktop; the ReputeMap tools appear under the 🔨 tools icon.
Cursor
Add to ~/.cursor/mcp.json (or .cursor/mcp.json inside a project):
{
"mcpServers": {
"reputemap": {
"url": "https://api.reputemap.com/mcp",
"headers": { "Authorization": "Bearer rmk_YOUR_KEY" }
}
}
}
Copy-paste-ready versions of all three configs are in the reputemap-examples repo.
Available tools
| Tool | What it does | Credits |
|---|---|---|
list_locations | Every location the org manages, with ids | 1 |
list_reviews | Reviews, filterable (location, rating range, unanswered, last N days) — includes published reply text | 1 |
get_review_stats | Per-location + totals: counts, average rating, 1–5 breakdown, unanswered, trailing-window activity | 1 |
send_review_request | Sends a real review-request email through the campaign engine (respects opt-outs; idempotent) | 1 |
get_usage | Current month’s credit usage | free |
MCP tool calls share the same 1,000 credits/month allowance as the REST API — plenty for daily use; get_usage tells you where you stand at any time.
Troubleshooting
| Symptom | Cause & fix |
|---|---|
401 Invalid or missing API key | Key typo, or the key was revoked — create a new one in Settings → API keys |
403 … requires an active paid plan | The org has no subscription — pick a plan (the 14-day trial counts) |
| Tool answers “Monthly API credit limit reached” | Credits reset on the 1st; check get_usage |
| Claude Desktop doesn’t show the tools | npx needs Node.js ≥ 18; fully restart the app after editing the config |
Is it safe?
The key only reaches data your org already owns: your locations, your reviews, your stats. The one write action — send_review_request — goes through the same suppression/opt-out engine as the in-app campaigns, so an over-eager AI can’t spam your customers. Revoke the key at any time and access dies instantly.