Your marketing department, inside your Claude.

A Model Context Protocol server at mcp.epinium.com. It exposes 41 read tools over your Amazon account plus live access to your Shopify and WooCommerce stores, a catalog of 100 marketing playbooks across 22 disciplines and, on the Business plan, write tools for workflows, Sponsored Products, Sponsored Brands and Sponsored Display, tasks and portfolios that only appear when you grant them — 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 live connection — your real Amazon account, or your Shopify or WooCommerce store. 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.

Only if you grant it. By default the assistant just reads. Write scopes exist — workflows:write and campaigns:write among them — and they are ticked by you when the key is issued: without them those tools are not even visible to it. With them it can create and edit workflows and Sponsored Products campaigns, ad groups, targets and product ads; edit Sponsored Brands and Sponsored Display (status, budget, name, bids, targets and negatives); create, approve and apply tasks; and manage portfolios and each campaign’s optimization targets. A new campaign is created PAUSED unless you explicitly ask for it enabled, budgets are checked against the marketplace minimum before reaching Amazon, and every change lands in the change log — including what Amazon rejected. Writing ships with the Business plan — on Free and Guru the MCP stays read-only. Your catalog is never edited. Full detail on the Epinium MCP page.

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 — including fees, net sales, margin before ads and refunds per product for sellers, and sell-in, fill rate and inventory for vendors — plus your own Shopify and WooCommerce stores, live. That is the boundary. Of the 100 playbooks, 27 are Amazon-specific and 62 are channel-agnostic — those work on figures you provide. Beyond those, 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, 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, Shopify and WooCommerce, 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.

Yes, since September 2026. On the Business plan, with the write scopes ticked, it creates and edits workflows and Sponsored Products campaigns — a new campaign is created paused unless you ask for it enabled — and it also edits Sponsored Brands and Sponsored Display, creates, approves and applies tasks, and manages portfolios and per-campaign optimization settings. Beyond Amazon, it works with your Shopify and WooCommerce stores live. We are not putting dates on what comes next: 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.