Epinium MCP

Access: Settings → MCP

The Epinium MCP lets an AI assistant query your Epinium data directly, with no exports and no code. You can ask it in plain language which campaigns have the worst ACOS or which searches are eating your budget, and it answers with your real figures.

It runs on the Model Context Protocol, an open standard for connecting assistants to data sources. Under the hood it uses the Epinium API, so it sees exactly the same data and honours the same permissions.

Read-only

The assistant can query your data, never change it. It cannot adjust bids, pause campaigns or edit products.

The server address

https://mcp.epinium.com/mcp

You will also find it in Settings → MCP, with a button to copy it.

How to connect it

There are two ways to give the assistant access, and which one applies depends on the client you use:

• Browser authorisation: you paste the server address, the assistant takes you to Epinium, you approve and that is it. There is no key to copy, and you can withdraw access whenever you like from Settings → MCP.
• API key: you create a key in Settings → API Keys and paste it into the client's configuration. This is the route for Claude Code and for your own integrations.

Claude (web and desktop app)

1. Open Claude's connector settings and add a custom connector
2. Paste https://mcp.epinium.com/mcp as the server address
3. Claude will take you to Epinium to authorise access: review the permissions it asks for and approve them
4. Check that it works by asking it to use the epinium_whoami tool

Custom connectors require a paid Claude plan.

Claude Code

Claude Code is configured from the terminal and uses an API key rather than browser authorisation:

claude mcp add --transport http epinium https://mcp.epinium.com/mcp \
  --header "Authorization: Bearer TU_API_KEY"

Replace TU_API_KEY with a key created in Settings → API Keys, with whichever permissions you want to give the assistant.

ChatGPT

ChatGPT's MCP connectors live in developer mode (Settings → Security and login), and they are only available on paid plans and from the web version.

1. Turn on developer mode under Settings → Security and login
2. In the connector settings, add a new connector
3. Paste https://mcp.epinium.com/mcp as the server address and leave the registration method as it comes: the connector signs itself up
4. ChatGPT will take you to Epinium to authorise access: review the permissions it asks for and approve them
5. Check that it works by asking it to use the epinium_whoami tool

What you have connected

Settings → MCP lists the assistants you have authorised, with which permissions, who approved them and when. From there you can withdraw access from any of them: it immediately stops being able to read your data, and you can authorise it again later if you want.

API keys are managed separately, in Settings → API Keys.

What tools it includes

The assistant sees one tool per resource your token reaches. The names are descriptive, so you can just ask for what you want in plain language.

Group	Tools	Permission
Catalog	Products, their Seller, Vendor and Advertising views, brands, countries and clusters	catalog:read
Catalog performance	Seller and Vendor product metrics	catalog:read
Advertising structure	Campaigns, ad groups, targets, product ads and search terms	campaigns:read
Advertising performance	Metrics for the five levels above	campaigns:read
Connections	Your Amazon connections	connections:read
Tasks	Epinium tasks and their items	tasks:read
Skills	The CMO Brain: Epinium's 100 marketing skills	skills:read
Account	epinium_whoami and the list of accessible accounts	always

Only the tools your token can use appear. If you create a key with campaigns:read alone, the assistant will not see the catalog or task tools: they do not fail, they simply do not exist for that key.

CMO Brain: Epinium's marketing brain

Beyond your data, the MCP serves the CMO Brain: 100 skills with the methods a CMO would apply, written so an assistant can read and follow them. They cover everything from advertising and SEO to pricing, retention, content and marketplaces, and the assistant consults them before advising you.

The difference shows: without them, an assistant answers with whatever it read online; with them, it follows the same criteria we work by and applies it to your figures. Ask it to review a campaign with a poor ACOS and it does not improvise generic advice: it loads the relevant skill and follows it.

They require the skills:read permission, which is ticked by default when you create a key.

Interactive tables

When you ask it for a list — products, campaigns, search terms — the assistant can show it as a table inside the conversation instead of as text.

With that table you can:

• Load more rows without spending assistant turns. The table fetches the next pages on its own, so working through a long catalogue does not consume conversation.
• Open a row to see its full detail, including the fields that do not fit in the table.
• Select several rows and hand them to the assistant with the Use N in chat button. From then on it reasons about those only: pick six products out of two hundred and ask about them, without copying a single ASIN.

What data it reaches

The same as the API, resource by resource. The full list of endpoints, with what each one returns, is in the API section.

Four things worth knowing when asking it for data:

• Metrics need a date range. Tell it the period you care about; otherwise the assistant will ask.
• You can ask for the day-by-day evolution, not just the total for the period. Useful for spotting trends rather than a single aggregate figure.
• The range cap depends on the granularity. With the period total, 366 days; day by day, 93. For targets and search terms, the heaviest resources, it drops to 93 and 31. Asking for more returns an error stating the exact limit.
• An empty figure is not a zero. If the assistant says a metric is unavailable, it means Amazon does not report it for that ad format, not that it is zero.

Questions it answers well

• Which campaigns have the worst ACOS this month?
• Which searches am I spending on without any sales?
• Which keywords are performing best and would be worth promoting to exact match?
• Which advertised products are not getting a single impression?
• Which of my products get traffic but do not convert?