# Amazon Selling Partner API MCP Server A Model Context Protocol (MCP) server for interacting with the Amazon Selling Partner API. This server
Everything the assistant can do here goes through one of these:
overview — authenticationcatalog — ordersinventory — reportsfeeds — financenotifications — productPricinglistings — fbaInstallation goes through your MCP client rather than a global install: point it at amazon-sp-api-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 7 environment variables: SP_API_CLIENT_ID, SP_API_CLIENT_SECRET, SP_API_REFRESH_TOKEN, SP_API_AWS_ACCESS_KEY, SP_API_AWS_SECRET_KEY, SP_API_MARKETPLACE_ID, SP_API_REGION. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Amazon Selling Partner API's toolset — overview, catalog, inventory and 3 more — is a fair guide to whether it matches your workflow. It is maintained by mattcoatsworth; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Amazon Selling Partner API's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| overview | authentication |
| catalog | orders |
| inventory | reports |
| feeds | finance |
| notifications | productPricing |
| listings | fba |
{
"mcpServers": {
"amazonseller": {
"command": "npx",
"args": ["-y", "amazon-sp-api-mcp-server"],
"env": {
"SP_API_CLIENT_ID": "your-value",
"SP_API_CLIENT_SECRET": "your-value",
"SP_API_REFRESH_TOKEN": "your-value",
"SP_API_AWS_ACCESS_KEY": "your-value",
"SP_API_AWS_SECRET_KEY": "your-value",
"SP_API_MARKETPLACE_ID": "your-value",
"SP_API_REGION": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SP_API_CLIENT_ID | Configuration value read at startup. | Optional |
| SP_API_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| SP_API_REFRESH_TOKEN | Credential the server authenticates with. | Yes |
| SP_API_AWS_ACCESS_KEY | Credential the server authenticates with. | Yes |
| SP_API_AWS_SECRET_KEY | Credential the server authenticates with. | Yes |
| SP_API_MARKETPLACE_ID | Configuration value read at startup. | Optional |
| SP_API_REGION | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.