Install a client
Any tool that speaks MCP over HTTP and lets you set a request header can connect. Three are documented here because they are the three the app generates a ready-made snippet for.
Pick your client
| Client | How it connects | Needs Node.js |
|---|---|---|
| Claude Code | One terminal command | No |
| Cursor | A .cursor/mcp.json file | No |
| Claude Desktop | Config file, through a bridge | Yes |
| Other clients | Manually, if it supports headers | Depends |
ChatGPT and claude.ai in the browser cannot connect yet. Both accept custom MCP servers only through a sign-in flow, with no field for a key. There is nowhere to put the credential this server uses. See Other clients.
Before you start
You need two things, and both come from the app:
- The server address —
https://upsell.avada.io/mcp - A key — created in Settings → Connect to AI, shown once. See Authentication.
Your store also has to be on a paid plan. The Connect to AI section is not shown otherwise.
Your server name is per-store
Every snippet names the server aov-upsell-your-store, taken from your .myshopify.com domain.
For northwind-supply.myshopify.com that is aov-upsell-northwind-supply.
If you run more than one store, do not shorten these to aov-upsell. AI clients key their server
list by name: the second config would silently replace the first, and nothing in the answers would
tell you which store you were looking at.
After you connect
Do not trust "no error" as proof. Check both halves — that the client sees the server, and that the key is accepted:
-
The client sees the server. Each page below says where to look —
/mcpin Claude Code, Settings → MCP in Cursor, the tools icon in Claude Desktop. You should see the server listed with 10 tools. -
The key is accepted. Ask a question only this store can answer:
What free gift campaigns am I running?
A real answer means the whole chain works. A refusal means the server was reached but the key was not accepted — go to Troubleshooting, which tells the two apart.
Changing the address or the key
Remove the server and add it again rather than editing the entry in place. Clients cache what they learned when the server was first registered — the tool list, and in some cases the credential — and editing a URL does not always clear it. Removing and re-adding always does.