rebuy_get_ collection_ productsGet products from one or more Shopify collections, optionally sorted by Rebuy.
See what Rebuy would recommend with a product, check your top sellers and trending products, test a data source against a real cart, and search your store the way shoppers do, all from your AI client.
PopMCPRebuy
Rebuy's documented API is all here: its AI product lists, your data sources, widget settings, Smart Search, Smart Collections, Meta Shops and analytics events. Long lists come back short and searchable, and product answers stay compact unless your AI asks for more.
28 tools in the full catalog: 26 read and 2 write. 24 load by default, and the rest are found with tool search.
rebuy_get_ collection_ productsGet products from one or more Shopify collections, optionally sorted by Rebuy.
rebuy_get_ complementary_ to_ viewedGet products that go with what one shopper viewed.
rebuy_get_ products_ by_ idGet specific products as Rebuy holds them, by id or handle.
rebuy_get_ purchased_ productsGet the products one customer bought before, the list behind Rebuy's Buy It Again.
rebuy_get_ recommended_ productsGet Rebuy's AI cross-sell picks: the products most likely to convert alongside the ones given.
rebuy_get_ similar_ productsGet products similar to one product, from Rebuy's AI.
rebuy_get_ top_ sellersGet the store's best selling products by Rebuy's sales data.
rebuy_get_ trending_ productsGet products trending in recent sales.
rebuy_get_ viewed_ productsGet the products one shopper recently viewed.
rebuy_get_ shopper_ productsSee one shopper in one call: what they bought, what they recently viewed and what goes with what they viewed.
rebuy_get_ smart_ cart_ settingsRead the store's Smart Cart settings: whether it is on, its layout, cross-sell widget, buy more save more tiers, progress bar and wording.
rebuy_get_ store_ snapshotGet the store's top sellers, trending products and Rebuy's recommended products in one call.
rebuy_list_ data_ sourcesFind the store's data sources: Rebuy's built-in ones and the merchant's own rulesets, also called custom endpoints.
rebuy_list_ smart_ flowsList the store's active Smart Flows: the popups, banners and targeted offers shown to shoppers.
rebuy_quick_ view_ searchGet autocomplete suggestions for what a shopper is typing, as in the Smart Search Quick View.
rebuy_search_ contentSearch the store's articles and blog posts through Smart Search.
rebuy_search_ productsSearch the store's products the way shoppers do, with the merchant's Smart Search settings applied.
rebuy_get_ smart_ collection_ productsList the products in one Smart Collection as shoppers see them, with filters and sorting.
rebuy_get_ smart_ collection_ settingsRead the Smart Collections settings in force for one collection, with any running campaign applied.
rebuy_run_ data_ sourceRun one of the merchant's data sources, also called custom endpoints or rulesets, and see what it would show this shopper.
rebuy_track_ eventRecord one shopper event in Rebuy's analytics, such as a product view.
rebuy_track_ events_ bulkRecord up to 100 shopper events in one call.
rebuy_get_ shop_ configRead the connected store's Rebuy setup: name, domains, currency, cache key, which features and integrations are on, and a short list of its Smart Cart and Smart Flows.
rebuy_get_ widget_ settingsRead all the settings of one Rebuy widget: its data source, layout, placement, discount, wording and styles.
rebuy_meta_ get_ collection_ trendingGet what is trending in one collection for Meta Shops.
rebuy_meta_ get_ recommendedGet recommendations for Meta Shops.
rebuy_meta_ get_ storefront_ trendingGet what is trending across the store for Meta Shops.
rebuy_list_ sourcesList every data source in the store as Rebuy returns it: the built-in ones and the merchant's own rulesets, with the names of the inputs each takes.
Credentials off one Rebuy screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.
In the Rebuy admin, open Settings, then API Keys, and copy a key. If there is none yet, click Create new API Key. Paste it into PopMCP, which checks it with Rebuy and finds your store from it, so there is nothing else to fill in.
••••••••••••3f7aexample-brand.myshopify.com••••••••••••3f7aReading is safe: nothing the AI reads changes your store. The only writes record analytics events, which join your real data, and connections start read-only so those stay off until you allow them. Rebuy has no API for editing widgets, rules or the Smart Cart, or for orders and sales reports. Each connection keeps to its one store.
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your Rebuy credential never leaves the server.
app.popmcp.com/mcpAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
What are my top sellers and trending products right now?
rebuy_get_store_snapshotok
Then just ask for the work
“What are my top sellers and trending products right now?”
“What would Rebuy recommend alongside the Classic Beanie?”
“Find my post-purchase data source and show what it returns for a cart holding product 562415992868”
“How is my Smart Cart set up, and which Smart Flows are running?”
“Search my store for hats under 50 dollars, in stock only, and show the filters shoppers get”
“What did customer 65069794 buy and view, and what goes with what they viewed?”
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
FAQ
What teams ask before putting Rebuy behind an AI client.
A Rebuy account and one API key. In the Rebuy admin, open Settings, then API Keys. PopMCP uses the key to find your store, so usually that is all you paste.
No. Rebuy's API can read widget and Smart Cart settings but has no way to change them, so those edits stay in the Rebuy admin. The AI can tell you what to change.
No. Rebuy's documented API has no calls for orders or reports. It can show what a customer bought as a list of products, and your top sellers and trending products.
Only analytics events, such as recording that a shopper viewed a product. They join your real data and feed recently viewed lists. New connections are read-only, which removes those tools until you allow write actions.
They only work if the store has those features on. Ask the AI to read your store's Rebuy setup, which shows whether each one is on.
Rebuy's Meta Shops recommendation calls ask for a private key. You only need it for those tools, and can ask Rebuy for it. Everything else works with the key from your API Keys page.
Some Rebuy calls take the key in the address, and that is how Rebuy designed them. PopMCP stores the key encrypted, sends it only to Rebuy from its servers, and removes it from every answer the AI sees.
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
Connect Rebuy in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Rebuy on the consent screen. The Rebuy tools are then available in that session, and no Rebuy credential is stored on your machine.
Loading 28 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 24-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.
A tool is something your AI calls, and there are 28 here. A trigger is something PopMCP watches for you: 3 Rebuy events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Rebuy.
Launch a hosted MCP endpoint for Rebuy, keep tool access under control, and start testing real workflow prompts right away.