Seller Labs Amazon MCP
com.sellerlabsPublished by sellerlabs.comOfficial publisherv1.0.0Updated Nov 5, 2026
Amazon Seller Central + Ads data for AI agents: true SKU profit with COGS, inventory, ads, orders.
Overview
Remote MCP endpoint from Seller Labs that gives AI assistants Amazon Seller Central and Ads data, including SKU-level profit with COGS, inventory, ads and…
- What you can do
- Read Amazon seller business data: SKU-level profit calculated with COGS, inventory, advertising and orders.
- No tool list is published, so the exact operations are not documented; expect read-style queries over Seller Central and Ads data.
- Access is through a hosted endpoint with OAuth sign-in rather than a local package.
- When to use it
- Useful when an assistant should answer questions about Amazon marketplace performance — which SKUs are profitable, how inventory and ads relate to orders — without exporting reports by hand. Suited to sellers or agencies already using Seller Labs tooling.
- Requirements
- A remote streamable HTTP endpoint at the provider's hosted API; no local runtime or package needed. OAuth authentication is required, so an Amazon seller account connected through Seller Labs is expected. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Seller Labs Amazon MCP in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.sellerlabs%2Famazon-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"seller-labs-amazon": {
"type": "http",
"url": "https://ignite-api.sellerlabs.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestNov 5, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.