Ava Research

Reply — Docs

Draft a response to any review, right through Muse.

Reply is a hosted MCP (Model Context Protocol) server. Paste a customer review or piece of feedback, and Reply drafts a professional response in the owner's own stored voice — gratitude for wins, de-escalation for misses, never admitting fault or offering compensation on the owner's behalf.

Free. No paid plan. get_methodology works without an account. Everything else requires a free account, created with a one-time code sent to your email — no password, no payment details.

Endpoint

https://func-reply-prod-vvehgl.azurewebsites.net/api/mcp

JSON-RPC 2.0 over HTTPS POST. Methods: initialize, tools/list, tools/call. MCP protocol version 2025-06-18.

Authentication

Sign-in uses OAuth with Microsoft Entra External ID: Muse gets an access token from Entra, and the server accepts only Entra-issued tokens with the Reply.ReadWrite scope. The server publishes protected-resource metadata (RFC 9728) and returns 401 with a WWW-Authenticate header pointing to it. Tokens are validated on every call: signature, issuer, audience, expiry, and scope. Every tool except get_methodology needs a signed-in user.

Tools

  • get_methodology · Sign-in: No
    Explains how Reply works: the drafts-never-posts rule, the never-admits-fault/never-offers-compensation rule, and what "not stated" means.
    Inputs: none.
    Example: "What won't Reply do in a response?"

  • set_voice · Sign-in: Yes
    Stores the owner's brand voice for response drafts: business name, an optional tone description, an optional sign-off, and optional standard phrases.
    Inputs: businessName (required), tone, signOff, standardPhrases.
    Example: "Set my voice: warm, a little informal, sign off '— The Riverside Cafe team.'"
    Errors: invalid_params.

  • draft_response · Sign-in: Yes
    Drafts a professional response to a pasted customer review. Extracts customerName and starRating only when explicitly and unambiguously stated — otherwise left honestly unset.
    Inputs: reviewText (required), customerName, starRating.
    Example: "Waited 40 minutes for a table, food was great once it came. 3 stars."
    Errors: invalid_params.

  • revise_response · Sign-in: Yes
    Revises a previously drafted response with a plain-words instruction.
    Inputs: responseId (required), instruction (required), revisedText (required).
    Example: "Apologize for the wait more directly."
    Errors: invalid_params, not_found.

  • list_responses · Sign-in: Yes
    Lists the owner's review+response records, newest first, optionally filtered by a customer-name substring match.
    Inputs: customerName (optional).
    Example: "What reviews have I responded to?"
    Errors: invalid_params.

  • delete_my_data · Sign-in: Yes · Permanent
    Owner-only, irreversible: deletes your voice profile, every review+response record, and every cached draft for your account.
    Inputs: none.
    Example: "Delete all my Reply data."

Errors

If the token is missing, expired, or lacks Reply.ReadWrite, tools that need sign-in return HTTP 401 with a WWW-Authenticate header. Tool errors come back as a result with isError set to true and a short, readable message; the codes are listed with each tool above.

Limits

  • No connector-specific rate limit is enforced or published.

  • delete_my_data is permanent — there is no undo, and Muse will ask for confirmation every time, never "always allow."

What it won't do

  • It never posts a response anywhere — every draft is yours to review and post yourself.

  • It never admits fault or offers compensation on your behalf.

  • It never invents a customer name or star rating.

  • It shares nothing with advertisers.

Questions? support@avaresearchllc.com · Back to Reply