Hosted Amazon Seller Central and Amazon Ads MCP server for Claude, ChatGPT, Cursor, and agents.
One address for any MCP client. You sign in once, after adding it.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Odel could not list its tools without signing in.
Agent Central connects the AI you already use to your Amazon Seller Central account. It is a hosted MCP server that gives Claude, ChatGPT, Claude Code, Cursor, and other MCP clients your Seller Central and Amazon Ads data through one connection at https://mcp.agentcentral.to/mcp.
This repository holds the public registry metadata and a local introspection stub. Your assistant connects to the hosted endpoint; the stub only lists the tool catalog.
Agent Central. One connection covers Amazon Ads (Sponsored Products, Sponsored Brands, Sponsored Display, DSP, and Stores) and Seller Central (sales and traffic, orders, inventory, inbound shipments, catalog, fees, settlements, and fulfillment), so Claude can answer questions that need both, such as TACOS by product or profit after Amazon fees and ad spend.
Amazon's own Selling Partner plugin for Claude has no Amazon Ads data, and Amazon's Ads MCP server has no Seller Central data. See Agent Central vs Amazon's Selling Partner plugin, tested on the same seller account.
Yes. Agent Central keeps your Amazon Ads history for as long as your account is connected, while Amazon's own Ads reports reach back only 60 to 95 days depending on the ad type. Synced Seller Central history is kept while the account is active, so once a year of history has built up, your assistant can compare any period with the same period last year by campaign, search term, or ASIN.
Yes. Agent Central covers 23 Amazon marketplaces, including the US, UK, Ireland, Germany, France, Italy, Spain, the Netherlands, Belgium, Sweden, and Poland, all included in one subscription. Amazon's Selling Partner plugin starts with US stores.
Yes. Each client gets its own workspace with its own Amazon connections and keys, so a key for one client can't read another client's data, and your team can switch between client workspaces in one dashboard. See Agent Central for agencies.
Claude. Copy the key's Connector URL, then in Claude open Customize > Connectors, choose Add custom connector, and paste it. Claude quickstart
Claude Code.
export AGENT_CENTRAL_API_KEY="ac_live_..."
claude mcp add --transport http agentcentral https://mcp.agentcentral.to/mcp \
--header 'Authorization: Bearer ${AGENT_CENTRAL_API_KEY}'
Connect Seller Central to Claude Code
ChatGPT. In ChatGPT web, open Apps, then Advanced Settings, turn on Developer Mode, choose Create App, paste the Connector URL, and set authentication to No auth. For read-only access, ChatGPT can instead connect with OAuth to https://mcp.agentcentral.to/mcp. ChatGPT quickstart
Other MCP clients.
{
"mcpServers": {
"agentcentral": {
"url": "https://mcp.agentcentral.to/mcp",
"headers": {
"Authorization": "Bearer ac_live_<YOUR_API_KEY>"
}
}
}
}
Never put an API key or Connector URL in a public repo, chat, or issue.
More at agentcentral.to/security.
Agent Central returns Amazon's data, source fields, deterministic metrics with stated formulas, and audited write results. Your assistant does the reasoning and decides what to do with them.
The hosted endpoint exposes 176 domain-scoped tools across advertising, inventory and orders, catalog, finance, and fulfillment, plus utilities, for 181 tools in total. See the tool reference.
This repo ships a minimal stdio MCP server so directories and clients can list the public tool catalog without an Agent Central account. It does not execute tool calls; every call returns a pointer to the hosted endpoint and setup guide.
The stub is not published to npm. Clone this repository or use Docker if a directory or client needs local stdio introspection. For real use, configure the hosted endpoint above.
docker build -t agentcentral-mcp .
docker run --rm -i agentcentral-mcp
Or with Node:
npm install
npm run build
node dist/index.js