Paid & retail media
21- paid-media
- retail-media
- trade-shopper
The brain of a CMO — 100 marketing playbooks and a router that picks the right one — wired to your live Amazon account. Free to start, inside the Claude or ChatGPT you already use.
Free to start · No credit card · Read-only
What our clients say













Most commerce MCPs hand your AI the raw API and wish it luck. Epinium hands it the playbook: the formula, the threshold that makes it valid, and the reason not to trust Amazon’s suggestion.
Every division is a real folder of versioned playbooks, not a category label. This is the whole map — the part a wrapper around the Amazon API has none of.
A playbook is only useful if it knows the tool you actually run on. These are the platforms named inside the catalog — the retail-facing ones first. Epinium is not connected to them, and it does not need to be: read on.
The CMO AI reaches your data five ways, and tries them in this order. Amazon is the deep one — nine years already sitting in our database. Everything else routes through your assistant, which already sits in the middle of your stack.
Amazon Seller, Vendor and Ads: nine years of history already ingested into our own warehouse. Ask about the last 24 months and the answer doesn’t queue against any API.
Your store and marketing channels, connected to Epinium and queried live. Shopify already; more every week. A channel moves to deep when it earns it — that’s a threshold, not a promise.
If your Claude or ChatGPT has a connector for Google Ads, HubSpot, Shopify, Meta or GA4 — most of this wall has one — the playbook works straight against that data. Epinium brings the criterion; your host brings the reach. Nothing passes through us.
No connector for it? An assistant with browser control can open the platform in your own session, read the numbers off the screen, and make the change you approve — with the playbook telling it what to look at, what the threshold is, and what not to touch.
Neither one available? Export the CSV, paste the table, drop the screenshot — it will ask you for exactly what it needs. 62 of the 100 playbooks are channel-agnostic by design: they run on the figures you bring, whatever tool they came out of.
Plus Klaviyo, Criteo, Mirakl, Ahrefs, Amazon DSP, Brand Analytics, Merchant Center and dozens more named across the catalog. Two of the five steps above are Epinium connections (deep integration, light connection) — the other three are not, and don’t need to be. Whoever acts is your assistant or your platform; whoever approves is you — the same governance rule as everywhere else on this page.
Every commerce MCP can call Amazon. These are the parts that need nine years of operating the channel behind them.
This is what happens when you connect Epinium to your AI host. None of it requires code, and none of it changes anything in your Amazon account.
It reads your live commercial data from inside a chat window. That deserves more than a reassuring sentence.
Twenty-two disciplines, backed by the experience of 500 brands. Not a data pipe — a marketing department. No card required.
Start free →Start on the free plan — the full playbook catalog, one live connection, no card.
The same CMO AI and the same account, inside the Claude or ChatGPT your team already uses. Free to start.
ExploreOptimise your Amazon listings with AI in seconds. Generate high-converting listings in any language with perfect copywriting and the most relevant keywords.
ExploreSupervised agents for your Sponsored Ads: they propose bid, keyword and budget changes, and you approve each one. Built to grow profit (TACOS), not just cut ACOS.
ExploreNo-code automations for your Amazon account: connect the data, set the trigger, and let the process run on its own — with the checkpoints you decide.
ExploreActs as your personal account consultant, analyzing cross-data from sales, advertising, consumer behavior, catalog, and operations. It detects patterns and areas for improvement, and offers personalized, strategic recommendations to optimize every aspect of your ecommerce and marketplace business.
Explore Beyond the toolsA fully personalized platform with dedicated workspaces for every role in your team — catalog, operations, advertising, and analytics — all connected through one AI chat.
ExploreA Model Context Protocol server at mcp.epinium.com. It exposes 41 read tools over your Amazon account plus a catalog of 100 marketing playbooks across 22 disciplines, callable from Claude, ChatGPT or any MCP-compatible host.
Yes. The free plan gives you MCP access with the full 100-playbook pool and one read-only connection to your real Amazon account. It needs an Epinium account, not a card. It carries a monthly token allowance that every MCP request draws from.
Every request to the MCP. Reading a playbook, listing campaigns, querying an ASIN — each one draws from your monthly allowance. Paid plans carry larger allowances.
The MCP stops answering until your next monthly cycle. You can wait for the renewal, buy an add-on pack, or move to a plan with a larger allowance — nothing is billed beyond your plan unless you ask for it.
No — on any plan. Version 1 is read-only by construction: five scopes, all read, and no mutating endpoints. It reads your data, applies the playbook and hands you a recommendation. You decide and you execute.
Any MCP-compatible host over remote HTTP: Claude Desktop, claude.ai, Claude Code, ChatGPT, Cursor and custom agents. Interactive tables render in Claude Desktop and claude.ai. Local stdio transport is not supported.
Issue a key in your account settings with the scopes you want, then run claude mcp add --transport http epinium https://mcp.epinium.com/mcp with an Authorization: Bearer header. In Claude Desktop: Settings → Connectors → Add MCP server, same URL. OAuth 2.0 also works and is the better route if you would rather not handle a key.
Amazon: Seller Central, Vendor Central and Advertising, across your connected marketplaces. That is the boundary. Of the 100 playbooks, 27 are Amazon-specific and 62 are channel-agnostic — those work on figures you provide. There is no multi-platform connector layer, and we do not pretend there is.
Because the brain runs inside your assistant, and the connection does not have to be ours. Three routes, in the order it will try them: 1) if your Claude or ChatGPT already has a connector for that tool — Google Ads, HubSpot, Shopify, Meta, GA4 — the playbook works directly against that data, and none of it passes through Epinium; 2) if there is no connector, an assistant with browser control can open the platform in your own session, read the numbers off the screen and make the change you approve, with the playbook telling it what to look at and what not to touch; 3) failing both, it asks you for an export or a screenshot — 62 of the 100 playbooks are channel-agnostic by design and run on the figures you bring. None of the three is an Epinium connection outside Amazon, and in all three the acting is your assistant’s and the approving is yours.
A versioned document with the method: the formula, why that formula and not a simpler one, the statistical threshold that makes it valid, the confidence level, and an explicit What NOT to do. There are 100 of them, backed by 216 reference documents. That is the part an API endpoint cannot hand you.
That is the direction. More channel connections are being built, and write permissions are next — scoped by domain and gated by an approval step. After that you will be able to create and edit Epinium workflows straight from the MCP, with playbooks written for building them. We are not putting dates on any of it: what this page describes as working today is what works today.
Yes. Authentication is OAuth 2.0 or a scoped API key, and the tool surface is covered by an executable multi-tenant contract test so one account cannot read another’s data.