aov-post-purchase-upsell
🤖 MCP
Overview

MCP server

Connect Claude to this store and ask about your upsell offers in plain language — "how much extra revenue did my post-purchase offers make last week?" — and get the answer from your own live data instead of a guess.

MCP (Model Context Protocol) is the standard AI clients use to reach an outside data source. AOV Post Purchase Upsell runs one, so Claude can read your offers and results directly.

MCP is included in every plan, including Free.

One endpoint

https://aov-post-purchase.firebaseapp.com/ppu

You never type this by hand. The app shows you the exact command (Claude Code) or URL (Claude Desktop) to copy, in Settings → AOV MCP.

What it can do

Eleven tools, covering three kinds of question:

Ask aboutTools
Your offers — what exists, how it is set up, what it sellssearch_offers, list_offers_by_priority, count_offers, get_offer_detail, get_offer_stages
Your results — revenue, views, claims, conversionget_offer_summary, get_offer_stats, get_top_offers, get_shop_lifetime_stats, get_offer_coverage
What to sell next — bought-together history and best sellersrecommend_products

The numbers match what you see in the app. get_offer_summary returns the same figures as the Analytics dashboard; get_shop_lifetime_stats returns the same figures as the Statistics card on Home.

What it cannot do

Every tool is read-only. There is no tool that creates, edits, activates, pauses, duplicates, deletes or reorders an offer, and none that changes a discount, a trigger, or an order.

If you ask Claude to turn an expired offer back on, it will tell you that has to be done in the app and give you the link to that offer. It cannot do it for you, and it will not pretend otherwise.

It also cannot reach anything outside this store. The connection is pinned to one shop by the token, so Claude never sees your other stores, your other apps, or another merchant's data.

Which AI clients work

ClientSupported
Claude CodeYes — setup
Claude DesktopYes — setup
Claude on the webYes, through the same custom connector flow as Desktop
Cursor, VS Code, ChatGPT, other clientsNot yet
⚠️
Other MCP clients are refused during setup, not silently broken. The server only accepts sign-in callbacks from Claude and from your own machine, so a client outside that list fails while registering rather than connecting and then returning nothing.

The safety contract

  • Reads only. Nothing Claude does through this connection can change your store.
  • This store only. One connect code, one shop. It never reaches your other stores or apps.
  • Revoke at any time. Disconnect in the app cuts access immediately — the next thing Claude tries comes back refused. There is no cache to wait out.
  • Nothing is entered in the chat. You approve the connection in a browser tab on your own admin, not by pasting a secret into a conversation.

Where next

  • Authentication — how the connect code works, and how to cut access
  • Install — connect Claude Code or Claude Desktop
  • Tool guide — what to ask, and how questions map to tools
  • Tools reference — every tool, its inputs, and what it returns
  • Recipes — four whole questions, tool by tool
  • Store API — the same data over plain HTTPS, for a script or an integration
Product
Install AppWebsiteAvada Apps
Resources
DocumentationFAQPrivacy Policy
Company
Avada GroupContact
© 2026 Avada Group. All rights reserved.