Amazon SP-API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level - debug, info, warn, or error | info |
| CATALOG_PATH | Yes | Absolute path to the models subdirectory within the cloned selling-partner-api-models repository | |
| SP_API_BASE_URL | Yes | Amazon SP-API base URL for your marketplace (e.g., https://sellingpartnerapi-na.amazon.com) | |
| SP_API_CLIENT_ID | Yes | Your Amazon SP-API client ID from Amazon Developer Console | |
| SP_API_OAUTH_URL | No | Amazon OAuth endpoint | https://api.amazon.com/auth/o2/token |
| MAX_RESPONSE_TOKENS | No | Maximum tokens for API responses | 25000 |
| SP_API_CLIENT_SECRET | Yes | Your Amazon SP-API client secret from Amazon Developer Console | |
| SP_API_REFRESH_TOKEN | Yes | Your Amazon SP-API refresh token from either Amazon Developer Console or OAuth authorization flow |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute-sp-apiC | Execute Amazon Selling Partner API requests with specified endpoint and parameters |
| explore-sp-api-catalogC | Get information about SP-API endpoints and parameters |
| execute-external-apiB | Execute HTTP requests to external REST APIs (non-Amazon APIs) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have distinct purposes: one executes SP-API calls, one explores the SP-API catalog, and one executes external APIs. The only potential overlap is between execute-sp-api and execute-external-api, but the domain distinction (Amazon vs non-Amazon) is clearly stated in descriptions.
All tool names follow a consistent kebab-case verb-noun pattern: execute-sp-api, explore-sp-api-catalog, execute-external-api. The verb choices (execute, explore) are appropriate and predictable.
Three tools is a reasonable minimum for a generic API gateway that covers execution and discovery. However, the external API tool feels slightly out of scope for an Amazon SP-API server, making the set a bit ad hoc rather than perfectly scoped.
The combination of execute-sp-api and explore-sp-api-catalog provides complete coverage for generic SP-API interactions: discovery and execution. There are no obvious gaps for the stated purpose, though dedicated helpers for common operations are absent and the external API tool is extraneous.