Amazon Seller Operations

io.github.atul0016Published by GitHub account atul0016v0.1.1Updated Oct 24, 2026

Amazon account health, listing, FBA inventory, fee, PPC, review, and appeal intelligence.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Local MCP server giving an assistant Amazon seller operations intelligence: account health, listings, FBA inventory, fees, PPC, reviews and appeals.

What you can do
  • Account health and appeals: surface account health signals and appeal-related intelligence.
  • Listings: work with Amazon listing information.
  • FBA inventory: inspect FBA inventory data.
  • Fees and PPC: review fee and advertising (PPC) intelligence.
  • Reviews: look at review-related information for seller products.
  • No tool list is published, so exact actions are not documented.
When to use it
Worth considering if you run an Amazon seller business and want an assistant to help interpret account health, listings, FBA stock, fees, advertising and reviews in one place. Less useful if you only need a single narrow Amazon task or prefer a free, openly documented server.
Requirements
Runs locally over stdio, via uvx from the PyPI package or the published Docker image; desktop only. Requires a paid license key supplied in EARNALL_MCP_LICENSE_KEY, obtained from the vendor's purchase page. Optional EARNALL_MCP_ACTIVATION_ID and EARNALL_MCP_LICENSE_API variables configure activation and the license validation endpoint.
Before you install
It is a paid, license-gated product: a license key is required and is validated against a remote endpoint, so the key and an install/activation identifier are sent to the vendor. The license API endpoint can be overridden by environment variable, so verify it points where you expect. No tool list is published, so what it reads or changes in your seller data cannot be confirmed in advance.

Installation

In SourceWeft

  1. Open Amazon Seller Operations in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.