amazon-ads-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is amazon-ads-mcp-server?

The amazon-ads-mcp-server is a tool that allows users to connect to their Amazon Advertising Data by integrating their account with MarketplaceAdPros, providing access to various advertising resources and reports.

how to use amazon-ads-mcp-server?

To use the amazon-ads-mcp-server, you need to configure it in your MCP client by adding the necessary server configuration and environment variables, including your Bearer token from MarketplaceAdPros.

key features of amazon-ads-mcp-server?

  • Access to advertising resources in Sponsored Products, Sponsored Brands, and Sponsored Display.
  • Ability to query reports using plain English.
  • Recommendations and experiments available with a purchased subscription plan.
  • Streamable HTTP MCP Server option for easy integration.

use cases of amazon-ads-mcp-server?

  1. Integrating Amazon Advertising data into custom applications.
  2. Analyzing advertising performance through detailed reports.
  3. Utilizing Marketplace Ad Pros recommendations for campaign optimization.

FAQ from amazon-ads-mcp-server?

  • What is required to use the amazon-ads-mcp-server?

You need a valid Bearer token from MarketplaceAdPros and a compatible MCP client.

  • Can I use it without a subscription?

Basic functionalities may be available, but full access to recommendations and advanced features requires a subscription.

  • Is there support for debugging?

Yes, the MCP Inspector tool is recommended for debugging and provides a URL for accessing debugging tools in your browser.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Gpt Scrambler

2 days ago
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