amazon-orders-mcp is an unofficial MCP server for Amazon order history, line items,
and transactions, built on amazon-orders. It gives your AI assistant
tools for your Amazon account, available from Claude and any other MCP client.
The server never sees your credentials. When you sign in, a browser window opens on Amazon's own page, and the server
reuses the session that leaves behind. Signing in needs a display, so run the server on the machine you sign in on. On a
machine without one, like a server or a container, sign in with
amazon-orders login instead.
Note: This server reads its data through
amazon-orders, which works by parsing data from Amazon's consumer-facing website. As Amazon provides no official API to use, older versions may break at any time, so it's recommended that you use the latest version.
Installation
amazon-orders-mcp is available on PyPI and is run
with uvx, so there's nothing to install up front. Add it to your AI assistant:
Claude
Claude Desktop: download amazon-orders-mcp-<version>.mcpb from the
latest release and open it.
Claude Code:
claude mcp add amazon-orders -- uvx amazon-orders-mcp
ChatGPT
ChatGPT Desktop: in Settings → Plugins, add an MCP server of type STDIO, with uvx as the command and
amazon-orders-mcp as its argument.
Codex:
codex mcp add amazon-orders -- uvx amazon-orders-mcp
Other Clients
Any client that runs local MCP servers can use this JSON, or amazon-orders-mcp as the command if you've
installed it with pip install amazon-orders-mcp:
{
"mcpServers": {
"amazon-orders": {
"command": "uvx",
"args": ["amazon-orders-mcp"]
}
}
}
Remote Clients
For clients that connect to a server instead of running one, the server can also serve Streamable HTTP:
uvx amazon-orders-mcp --transport streamable-http
It listens at http://127.0.0.1:8000/mcp. See --help to change that, or to require a bearer token (required off
loopback).
Docker
docker build -t amazon-orders-mcp .
docker run -i --rm -v amazon-orders:/home/app/.config/amazonorders amazon-orders-mcp
A container has no display, so sign in with the login target first. See the Dockerfile for how.
Basic Usage
Just ask your assistant about your orders, and it will use the following tools:
| Tool | Returns |
|---|---|
sign_in |
Opens a browser window for you to sign in to Amazon, when you ask |
get_order_history |
A batch of orders by year, time filter or order type, optionally detailed |
get_order |
One order, by order number |
search_orders |
A batch of items by product, order number, address or recipient, any year |
get_tracking |
A shipment's carrier and tracking number, from an order's shipment ID |
get_invoice_pdfs |
An order's invoice and credit note PDFs, where the seller issues them |
get_transactions |
A batch of payment transactions over a number of days, or for an order |
get_gift_card_balance |
The current Gift Card balance |
get_gift_card_activity |
Gift Card activity over a number of days |
get_prime_payments |
Prime membership fee charges, each with its order number |
get_family_members |
Amazon Household members whose orders you can view, like Teen accounts |
get_config |
The settings your assistant can change, and their values |
update_config |
Changes a setting, like the default Amazon site (e.g. amazon.co.uk) |
check_session |
Whether you're signed in, on each Amazon site you have a session for |
Order history and transactions come back in batches of limit results (25 by default, and a batch can run up to a
page over), with a cursor your assistant passes back to get the next batch.
Every tool that reads Amazon takes an optional site, like amazon.de, so your assistant can read each Amazon site
you shop on from one server, e.g. "my last amazon.de orders". Without it, tools read your default site, the domain
setting. Each site has its own sign-in, so ask your assistant to sign you in to each one.
Configuration
Ask your assistant to change a setting, such as the default Amazon site (e.g. amazon.co.uk) or the browser to sign in
with. Settings are shared with the amazon-orders CLI, so it follows the same changes. See
Supported Sites for the sites
amazon-orders can read.
Documentation
For more on the data the server returns, amazon-orders's official documentation is available
at Read the Docs, including the
Order entity's fields
and troubleshooting.
Contributing
Want to contribute financially? If you've found amazon-orders-mcp
useful, sponsorship would
be greatly appreciated!
Metadata
Release files for amazon-orders-mcp 1.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| amazon_orders_mcp-1.5.0.tar.gz | 26.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| amazon_orders_mcp-1.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.6 kB
Release files / amazon_orders_mcp-1.5.0.tar.gz
| Download URL | amazon_orders_mcp-1.5.0.tar.gz |
|---|---|
| Size | 26.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4f8796aa1684b5449e10418cedfec81c73f4ce95c92689636f912a181af5084
|
|
BLAKE2b-256 checksum How to use checksums |
237a2233f51f85163375d20798a8477ee9b444e96641654e7fe19810ecb6b8e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / amazon_orders_mcp-1.5.0-py3-none-any.whl
| Download URL | amazon_orders_mcp-1.5.0-py3-none-any.whl |
|---|---|
| Size | 27.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
694dccc7e171bd0fbdc9efef9c1c1ebe041865dc00fc158a2448b5646513ccf4
|
|
BLAKE2b-256 checksum How to use checksums |
468a9270911a1ff83facc6f2835e9198d838b65a35d432f33da09e7d83f0bbcf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for amazon-orders-mcp 1.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.