Skip to content
StarReview

Agents

StarReview lets AI agents manage Google review replies for a business through a single MCP endpoint, with the business owner's approval and StarReview's guardrails built in.

Why connect through StarReview

An agent can write a reply on its own. What it cannot do on its own is post it. Replying to a Google review as the business needs approved Google Business Profile access, which StarReview holds. Connect through StarReview and your agent gets:

  • Posting to Google Business Profile from StarReview's own infrastructure, under the business's identity
  • The business's own voice, learned from its past replies and owner edits
  • Human approval for sensitive and negative reviews, always
  • A sentiment check on every draft, so nothing goes out that should not
  • A full audit trail of every action the agent takes

Your agent never posts to Google

An agent drafts and submits. It never posts to Google itself. StarReview publishes every reply from its own infrastructure, after the owner approves, and at your preferred time if you set one. This keeps posting under one accountable system, with the guardrails and audit trail in one place.

Endpoint

https://mcp.starreview.ch/

Streamable HTTP MCP. Authenticate with a per-business bearer token in the Authorization: Bearer header, and send Accept: application/json, text/event-stream on every request. The same server is also reachable at https://api.starreview.ch/api/agent/mcp.

Tools

  • list_locations: the business locations connected to this token
  • list_unanswered_reviews: Google reviews still waiting for a reply
  • get_review_context: the full review plus any existing drafts
  • draft_reply: generate a reply in the business's voice
  • submit_reply_for_approval: put one of StarReview's drafted variants into the owner's approval queue, optionally editing its text, with an optional preferred post time
  • submit_own_reply: put your agent's own reply text into the owner's approval queue, with no StarReview draft; always human-approved, never auto-scheduled

The flow

  1. Your agent lists unanswered reviews and reads their context.
  2. It submits a reply, using StarReview's draft or its own text, with an optional preferred post time.
  3. The reply enters the owner's approval queue. Negative reviews always wait for a human.
  4. Once approved, StarReview posts the reply to Google from its own infrastructure, at your preferred time if you set one.

Connect from your code

StarReview is a standard streamable HTTP MCP server, so any MCP client can connect. From the Claude API, add it to mcp_servers and pass the business token as authorization_token:

{
  "model": "claude-sonnet-5",
  "max_tokens": 1024,
  "messages": [
    { "role": "user", "content": "Draft replies for my unanswered Google reviews." }
  ],
  "mcp_servers": [
    {
      "type": "url",
      "url": "https://mcp.starreview.ch/",
      "name": "starreview",
      "authorization_token": "sragt_your_business_token"
    }
  ],
  "tools": [
    { "type": "mcp_toolset", "mcp_server_name": "starreview" }
  ]
}

The MCP connector is in beta, so send the current MCP connector beta header (see Anthropic's MCP connector docs). Other MCP clients connect the same way: point them at the endpoint and set the Authorization: Bearer header.

Walkthrough

A typical run. Every tool call returns JSON; the shapes below are representative.

1. List what needs a reply. Call list_unanswered_reviews:

[
  {
    "reviewId": "a1b2c3d4-...",
    "starRating": 5,
    "text": "Super Service, sehr freundlich!",
    "reviewerName": "M. Keller",
    "reviewDate": "2026-07-01",
    "sentiment": "positive",
    "hasDraft": false
  }
]

2a. Let StarReview draft it in the business's voice. Call draft_reply with the reviewId:

{
  "variants": [
    { "variant": 1, "text": "Vielen Dank fuer die netten Worte, Herr Keller ...", "riskFlags": [] }
  ],
  "language": "de",
  "sentiment": { "bucket": "positive", "confidence": 0.95 },
  "approvalReason": "agent_draft",
  "wouldAutoPublish": true
}

Then commit a variant with submit_reply_for_approval ({ "reviewId": "...", "variant": 1 }), optionally overriding its text.

2b. Or bring your own text. Skip drafting and call submit_own_reply:

// request
{ "reviewId": "a1b2c3d4-...", "finalText": "Danke vielmals, Herr Keller!" }

// response
{ "submitted": true, "autoScheduled": false }

autoScheduled is always false for your own text: it always waits for a human.

3. A human approves, StarReview posts. The reply sits in the owner's approval queue. Once approved, StarReview publishes it to Google from its own infrastructure, at your preferred time if you set preferredPostAt. Negative reviews always wait for a human.

Plans

If a business already has a StarReview plan, its agent works within that plan. If you run an agency operating many client businesses, or you are building a product on top of StarReview, get in touch and we will set up the right plan for your volume.

Getting a key

Tokens are issued per business by the StarReview account holder. If you run an agency or an agent product and want to connect client businesses, get in touch and we will set you up.