How do I install Dev Latam?

Dev Latam is a local plugin. Install it using npm package: @codespar/mcp-amazon and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

What credentials does Dev Latam need?

Dev Latam requires the following credentials or environment variables: AMAZON_LWA_CLIENT_ID, AMAZON_LWA_CLIENT_SECRET, AMAZON_REFRESH_TOKEN, AMAZON_MARKETPLACE_ID, AMAZON_REGION, AMAZON_SELLER_ID. You can find setup instructions on the server detail page.

What AI apps work with Dev Latam?

Dev Latam uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Dev Latam MCP Server

by User

Developer ToolsUse Caution4.2LocalNew

Free

MCP server for Amazon Selling Partner API (SP-API) — orders, listings, catalog, inventory, finances

About

MCP server for Amazon Selling Partner API (SP-API) — orders, listings, catalog, inventory, finances

Security Report

4.2

Use Caution4.2High Risk

This is a monorepo for 109 MCP servers wrapping LATAM commerce APIs. The code is well-structured with proper authentication patterns (API keys, OAuth2, mTLS support) and no evidence of malicious intent or data exfiltration. Permissions (network_http, env_vars) are appropriate for the category. Minor code quality observations exist, but do not warrant significant penalties given the architecture's purpose. Supply chain analysis found 2 known vulnerabilities in dependencies (1 critical, 0 high severity). Package verification found 1 issue (1 critical, 0 high severity).

4 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

Unverified package source

We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.

What You'll Need

Set these up before or after installing:

Environment variable: AMAZON_LWA_CLIENT_ID

LWA client_secret paired with AMAZON_LWA_CLIENT_ID.Required

Environment variable: AMAZON_LWA_CLIENT_SECRET

Long-lived seller-authorized refresh_token exchanged for 1-hour LWA access tokens used as x-amz-access-token.Required

Environment variable: AMAZON_REFRESH_TOKEN

Default marketplace id. BR: A2Q3Y263D00KWC, US: ATVPDKIKX0DER, MX: A1AM78C64UM0Y8, CA: A2EUQ1WTGCTBG2. Required by most endpoints; can be overridden per-call.Optional

Environment variable: AMAZON_MARKETPLACE_ID

SP-API region: 'na' (default — Americas, incl. BR/US/MX/CA), 'eu' (Europe + India + MENA), 'fe' (Far East — JP/AU/SG).Optional

Environment variable: AMAZON_REGION

Default sellerId (merchant token) used by Listings endpoints. Can be overridden per-call.Optional

Environment variable: AMAZON_SELLER_ID

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-codespar-mcp-amazon": {
      "env": {
        "AMAZON_REGION": "your-amazon-region-here",
        "AMAZON_SELLER_ID": "your-amazon-seller-id-here",
        "AMAZON_LWA_CLIENT_ID": "your-amazon-lwa-client-id-here",
        "AMAZON_REFRESH_TOKEN": "your-amazon-refresh-token-here",
        "AMAZON_MARKETPLACE_ID": "your-amazon-marketplace-id-here",
        "AMAZON_LWA_CLIENT_SECRET": "your-amazon-lwa-client-secret-here"
      },
      "args": [
        "-y",
        "mcp-dev-latam"
      ],
      "command": "npx"
    }
  }
}