It's 2026, and apparently the thing you do in 2026 is add an MCP server to your product. So we did. CentralDesk now includes an MCP (Model Context Protocol) server that connects Claude directly to your seller account. You can ask questions about your catalog and tickets in plain English, and Claude can take actions on your behalf. Yes, your Amazon support tool now talks to your AI assistant. We're all living in the future.
Here's what it actually does, why it's useful, and how to set it up in about three minutes.
What You Can Ask Claude to Do
Once connected, Claude has read access to your full CentralDesk catalog and ticket data. That means you can ask things like: "How many of my products have fewer than five bullets?" or "Which ASINs are missing A+ Content?" and get a real answer instead of spending twenty minutes clicking through Seller Central reports. You can also pull the current bullet text for any ASIN and ask Claude to rewrite it, then open a ticket to have your CentralDesk expert implement the change.
On the ticket side, Claude can show you which cases have gone the longest without a reply from your expert, help you draft a clear description for a new issue, and then open that ticket directly. It can also post a reply to an existing ticket. So instead of typing out a case description from scratch, you can talk through the problem with Claude, let it write the summary, and submit it in the same conversation.
One important note on permissions: API keys are read-only for catalog data. Claude can open tickets and post comments, but it cannot modify your catalog or account settings. If you were hoping to give an AI assistant unsupervised access to your product listings, that's not what this is. Which is probably the right call.
How to Set It Up
First, generate an API key. Go to your Account page in CentralDesk, scroll to AI Assistant API Keys, give the key a label, and click Generate. Copy it immediately: it's shown once and not stored. Each key is scoped to one seller account, so if you manage multiple accounts, generate a separate key for each.
To connect on claude.ai, go to Settings, open the Connectors tab, and click Add custom connector. Give it a name (your store name works well) and enter this as the Remote MCP server URL, replacing YOUR_KEY_HERE with the key you just copied:
https://centraldesk.io/app/mcp/index.php?key=YOUR_KEY_HERE
Click Add. Claude will confirm the connection and list the available tools. The whole thing takes about two minutes if you already have your API key.
For Claude Desktop, open ~/Library/Application Support/Claude/claude_desktop_config.json and add the following, replacing YOUR_KEY_HERE with your key and my-store with a name for the connection:
{"mcpServers":{"my-store":{"type":"http","url":"https://centraldesk.io/app/mcp/index.php","headers":{"Authorization":"Bearer YOUR_KEY_HERE"}}}}
Restart Claude Desktop after saving and you're connected.
Why This Is Actually Useful
The honest case for this feature isn't that it's exciting technology. It's that Seller Central data is annoying to query. Getting a clear picture of your catalog's content health: how many ASINs have complete bullets, which ones have A+ Content, what the current listing copy actually says, requires pulling reports, formatting spreadsheets, or clicking through individual product pages. That's work that eats time without adding value.
The MCP integration makes that layer of work conversational. You ask a question, you get the answer, you can act on it in the same session. For sellers who are already using Claude for other parts of their workflow, this brings your Amazon account data into the same context without switching tools.
It's also a useful interface for teams. A founder who doesn't want to live in Seller Central can ask Claude what's going on with their catalog and get a plain-English answer. A marketing person can pull listing copy without learning where it lives in Seller Central. An agency managing multiple accounts can add each as a separate connector and query them independently from the same Claude session.
If you're already a CentralDesk customer, the feature is available now. If you're not already using CentralDesk, well, what are you waiting for? It's free to sign up and it's pretty neat even without this fancy MCP stuff.