Amazon Selling Partner API MCP Server

Created By
mattcoatswortha year ago
Overview

What is Amazon Selling Partner API MCP Server?

Amazon Selling Partner API MCP Server is a Model Context Protocol (MCP) server designed to facilitate interaction with the Amazon Selling Partner API, providing a standardized interface for accessing its functionalities.

How to use Amazon Selling Partner API MCP Server?

To use the server, install it via npm, configure your Amazon SP-API credentials in a .env file, and start the server using npm commands.

Key features of Amazon Selling Partner API MCP Server?

  • Authentication and authorization with Amazon SP-API
  • Comprehensive coverage of SP-API endpoints
  • Documentation resources for API reference
  • Tools for managing catalog, inventory, orders, reports, and more
  • Secure credential handling

Use cases of Amazon Selling Partner API MCP Server?

  1. Managing product listings and inventory on Amazon.
  2. Processing orders and generating reports for sales analysis.
  3. Accessing financial data and managing notifications related to sales activities.

FAQ from Amazon Selling Partner API MCP Server?

  • What are the prerequisites for using this server?

You need Node.js 16 or higher and valid Amazon Selling Partner API credentials.

  • How do I install the server?

You can install it using npm with the command npm install amazon-sp-api-mcp-server.

  • How do I configure my credentials?

Create a .env file in the root directory with your Amazon SP-API credentials as specified in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattcoatsworth
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago