Amazon SP-API MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP listener host for Streamable HTTP transport. | 127.0.0.1 |
| PORT | No | HTTP listener port for Streamable HTTP transport. | 3000 |
| LOG_LEVEL | No | Pino log level. | info |
| SP_API_REGION | Yes | Amazon SP-API region: na, eu, or fe. | na |
| SP_API_ENDPOINT | No | Explicit SP-API endpoint override, primarily for tests and proxies. | |
| MCP_BEARER_TOKEN | No | Optional HTTP bearer token, minimum 16 characters. | |
| SP_API_CLIENT_ID | No | Amazon SP-API LWA client ID. | |
| MCP_ALLOWED_HOSTS | No | Comma-separated HTTP Host allowlist; required for non-loopback binds. | |
| SP_API_MAX_RETRIES | No | Retry limit for 429 and transient 5xx responses. | 5 |
| SP_API_ACCESS_TOKEN | No | Short-lived access token; alternative to refresh token credentials. Not refreshed automatically. | |
| SP_API_ARTIFACT_DIR | No | Local artifact storage directory. | ./artifacts |
| SP_API_CLIENT_SECRET | No | Amazon SP-API LWA client secret. | |
| SP_API_REFRESH_TOKEN | No | Amazon SP-API seller refresh token. | |
| SP_API_MAX_CONCURRENCY | No | Maximum concurrent outbound SP-API requests. | 4 |
| SP_API_MAX_RESPONSE_BYTES | No | Maximum inline response size before artifact storage. | 1048576 |
| SP_API_REQUEST_TIMEOUT_MS | No | Per-request timeout. | 60000 |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List safe account metadata, including account names, regions, and marketplace participations. Credentials are never returned. |
| discover_operationsA | Search the version-aware Amazon SP-API registry. Use this before describe_operation or invoke_operation. |
| describe_operationA | Return the exact method, path, parameters, request body, and validation schema for an operation ID. |
| invoke_operationA | Execute an operation using a stable account name. Multiple-account configurations require accountName. Writes require confirm=true unless dryRun=true. |
| get_artifactA | Read a chunk from a large or binary result saved by invoke_operation or run_report. |
| run_reportA | Create a report for a stable account name, poll until completion, download and decompress it, then return an artifact reference. |
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 6 tools
Each tool has a clearly distinct purpose: listing accounts, searching operations, describing an operation, invoking an operation, reading artifacts, and running reports. The overlap between discover_operation and describe_operation is minimal because one is for search and the other for detail.
All tool names follow a consistent verb_noun snake_case pattern: list_accounts, discover_operations, describe_operation, invoke_operation, get_artifact, run_report. There are no mixed conventions or vague verbs.
With 6 tools, the set is well-scoped. It provides a minimal but sufficient abstraction for interacting with the large Amazon SP-API surface, covering account management, operation discovery and invocation, and report handling.
The tool set covers the full workflow: discover operations, describe them, invoke them, and retrieve artifacts. The run_report tool handles the report lifecycle, and get_artifact reads large results. Given the generic invoke_operation, there are no obvious dead ends.