LABSCO SUMMARY

Read/write separation you configure at the key.

The useful distinction here is that writes are a different class of tool with previews and audit logs behind them, and a key can be issued read-only — so you can let an assistant answer questions about spend and stock cover without also granting it the ability to change a price. Everything real happens on the hosted endpoint; cloning the repository gets you a catalog listing and nothing else.

What it is

A hosted MCP server for Amazon sellers, reached over Streamable HTTP at https://mcp.agentcentral.to/mcp. It connects to Amazon Ads and Seller Central through Amazon OAuth and returns factual seller data with source fields — the repository itself holds registry metadata and a stdio stub for introspection, not the working server.

What you get

Amazon Ads reporting: campaigns, ad groups, keywords, targets, search terms, placements, budget pacing, TACOS, DSP, Brand Store and Amazon Attribution
Seller Central operations: inventory, orders, returns, reimbursements, listings, suppressed listings, inbound shipments, and FBA/AWD stock facts
Catalog and listing quality: details, sales ranks, A+ Content status, variations, listing issues, reviews and keyword ranks
Money: finance, profitability, payment transactions, settlements, fulfillment, MCF shipping and MCF orders
Guarded write tools for supported Ads, catalog, listing, price, inventory-quantity and MCF operations, with previews, guardrails and audited results
The hosted endpoint exposes 141 domain-scoped tools and 145 production tools in total

Requirements

An agentcentral account, your Amazon Ads and Seller Central connected over Amazon OAuth, and a scoped API key. Add the endpoint to any HTTP-capable MCP client with an Authorization: Bearer ac_live_<YOUR_API_KEY> header; Claude custom connectors instead use a signed connector URL generated in the dashboard. Keys can be scoped read-only. Nothing to install — the repository's stdio stub only lists the catalog and never executes a call.

Setup effort

Paste a URL with a key — add the endpoint to your client

See installation options

USE CASES

01

Catching stockouts before they cost rank

Ask which SKUs are below 30 days of FBA cover, with current stock, inbound units, sales velocity and suppressed-listing status in the same answer.

02

Explaining where the ad budget went

Pull Sponsored Products search terms with spend, clicks, attributed sales and TACOS over a window, instead of exporting reports by hand.

03

Finding out why a listing stopped selling

Check suppressed listings and the source-provided suppression reasons alongside listing issues and sales rank.

04

Letting an assistant act, carefully

Use a scoped key with write access so budget or price changes go through preview and land in the audit log.

BEFORE YOU INSTALL

What to know first

Requires

A client that can reach a remote MCP server over HTTP

Where it runs

The documented client connects to a hosted endpoint.

INSTALLATION

Connect your client

Add the endpoint to your client.

Server setup

ENDPOINT URL

https://mcp.agentcentral.to/mcp

MCP Clients

Any MCP client — remote

ANY MCP CLIENT — REMOTE · JSON

{
  "mcpServers": {
    "agentcentral": {
      "url": "https://mcp.agentcentral.to/mcp",
      "headers": {
        "Authorization": "Bearer ac_live_<YOUR_API_KEY>"
      }
    }
  }
}

agentcentral