Deploy Amazon Seller MCP
Self-hosted Amazon Seller analytics MCP for Claude: SP-API + Ads v3.
Just deployed
/var/lib/postgresql/data
amazon-seller-mcp-1mjb
Just deployed
amazon-seller-mcp
Just deployed
Deploy and Host Amazon Seller MCP on Railway
Amazon Seller MCP is a self-hosted, single-tenant analytics service for one Amazon seller account. A worker ingests your Selling Partner API, Advertising API v3, and Data Kiosk data into your own Postgres, and a bearer-guarded remote MCP server exposes it to Claude so you can ask questions and get answers grounded in your real numbers.
About Hosting Amazon Seller MCP
This template provisions three components in one deploy: a Postgres database, a worker that runs scheduled ingestion (migrations run automatically on boot, followed by a backfill of trailing history), and an MCP web service exposed over HTTPS with a health check. Every credential is supplied by you at deploy time as an environment variable — nothing is shared and no data leaves your project. The worker owns all Amazon API calls, retries, pagination, and throttling; the MCP service only reads Postgres, plus one approval-gated write path for bid changes. Your Claude connector reaches the service at its public URL using a bearer token you control.
Common Use Cases
- Ask Claude where you are wasting ad spend, which search terms to harvest into exact keywords, and where paid ads cannibalize organic sales
- Pull a P&L snapshot with ACOS and TACOS measured against each SKU's break-even margin
- Check Buy Box status and Search Query Performance share on demand, and propose bid changes with a human-approved confirm step
Dependencies for Amazon Seller MCP Hosting
- A Postgres database (provisioned automatically by this template)
- Your own Amazon SP-API app (self-authorized) and Amazon Advertising API security profile
Deployment Dependencies
- Amazon Selling Partner API: https://developer-docs.amazon.com/sp-api/
- Amazon Advertising API v3: https://advertising.amazon.com/API/docs/en-us/
Implementation Details
The MCP service exposes a bearer-guarded /setup/ads-auth route so you can mint your Ads refresh token from the browser, and a /healthz endpoint for Railway's health check. Set MCP_BEARER_TOKEN (auto-generated by this template) in your Claude connector to reach the server; all other Amazon credentials are entered once at deploy time.
Why Deploy Amazon Seller MCP on Railway?
Railway provisions the database, worker, and MCP web service together and injects the database URL automatically, so the entire stack comes up from a single click with your credentials entered at deploy time — no local setup, no shared secrets, and no data custody by anyone but you.
Template Content
amazon-seller-mcp-1mjb
stevegustafson32/amazon-seller-mcpamazon-seller-mcp
stevegustafson32/amazon-seller-mcpADS_PROFILE_ID
ADS_LWA_CLIENT_ID
ADS_REFRESH_TOKEN
SPAPI_LWA_CLIENT_ID
SPAPI_REFRESH_TOKEN
ADS_LWA_CLIENT_SECRET
SPAPI_LWA_CLIENT_SECRET
