ReputeMap

What ReputeMap MCP server does

ReputeMap MCP server exposes Google review management functions to MCP-compatible AI clients. It works with the locations managed by the authenticated ReputeMap organization and does not provide cross-organization access.

The read side includes location IDs, review data, reply status, and review metrics. Reviews can be filtered by location, star range, unanswered status, or a trailing number of days. Results support paging, with up to 50 reviews per page. Location and organization statistics include review totals, average rating, a breakdown from one to five stars, unanswered counts, and recent activity.

The action side supports generating reply drafts, publishing an approved reply, and sending an individual review-request email. Draft generation saves suggestions in ReputeMap but does not publish them to Google.

How it works

The hosted endpoint is https://api.reputemap.com/mcp and uses Streamable HTTP with JSON-RPC 2.0. Authenticate with an API key in an Authorization: Bearer header; the X-API-Key header is also supported. Keys are created in ReputeMap under Settings → API keys and are available to workspace owners and administrators.

ReputeMap MCP server defines seven tools. list_locations, list_reviews, get_review_stats, and get_usage are read-only. draft_reply stores a draft, while publish_reply sends the exact approved text to Google and send_review_request sends one email through ReputeMap's campaign system.

Clients receive safety metadata for the tools. Publishing is marked destructive, and the email action is non-idempotent, so clients can request confirmation before running them. Published replies may be pending or rejected by Google's moderation system. A rejected reply includes policy information, and it is treated as unanswered in review filtering.

Setup and configuration

A paid ReputeMap workspace or the 14-day trial is required, and the trial requires a card. The API key begins with rmk_ and is displayed once. Revoking a key immediately removes its access.

The recommended setup connects an MCP client directly to the hosted endpoint. Claude Code, Claude Desktop, Cursor, Cline, VS Code with Copilot agent mode, Windsurf, Codex CLI, and Gemini CLI each have documented configurations in the source material. Configuration details differ by client, including fields such as url, httpUrl, serverUrl, and type.

For clients that only launch local processes, run the npm package @reputemap/mcp through npx with Node.js 18 or newer. Set REPUTEMAP_API_KEY for the stdio bridge. The bridge forwards requests to the hosted endpoint. The generic mcp-remote package can also be used with Claude Desktop.

Tools and capabilities

• list_locations: returns organization locations and the IDs required by other tools.
• list_reviews: retrieves newest-first Google reviews with owner replies and filtering options.
• get_review_stats: reports location-level and organization-wide review metrics.
• draft_reply: generates two or three suggestions using the saved business voice and sign-off, with optional instructions.
• publish_reply: publishes the exact text approved by the user and audit-logs the action.
• send_review_request: sends one review-request email while applying suppression and opt-out checks.
• get_usage: reports current-month credits, limits, and rate-limit information.

Limitations and notes

The API key only exposes the organization's own locations, reviews, and statistics. publish_reply replaces an existing owner reply, so approval should be explicit. If Google refuses a publish request, ReputeMap retains the text and returns a manual-required status.

Review requests are real emails. Existing suppression rules and opt-outs still apply; if the address was already requested for that location, no second email is sent and the credit is returned. ChatGPT connectors are not supported according to the provided material.