Amazon FBA Seller MCP Server - PROPAMP AI

Created By
PROPAMP-AI2 months ago
Amazon Seller Central MCP Server — PROPAMP AI — official Amazon Software Partner. Connect your AI agent directly to Seller Central to analyze profitability and costs, find growth opportunities, plan supply chains, and manage ads — 20x faster, saving thousands of dollars monthly. → Case studies and full feature list at propamp.ai
Overview

PROPAMP AI — Amazon Seller Central MCP Server

Connect your AI agent directly to your Amazon Seller Central. No manual exports, no copy-pasting data into chat.

Once connected, your agent can pull real inventory levels across FBA, AWD, and in-transit shipments, calculate sales velocity per marketplace, analyze ad spend and true profitability, break down all cost layers, and build supply plans — the kind of work that used to take a specialist two weeks now runs in half a day.

What FBA sellers are already doing with it:

→ Full Prime Day supply plans across 16 marketplaces — built in hours, not weeks

→ PPC and returns analysis that surfaces losses most sellers never see

→ Inventory gap analysis before stockouts happen

→ Cash flow and COGS planning with real numbers, not estimates

The agent works with your actual data, audits its own calculations, and tells you exactly what to do and why. You stay in control — you verify, you decide.

Start with one task. Check the output. Then see what else makes sense.

Case studies and full feature list at propamp.ai

Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
PROPAMP-AI
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago