Walled gardens

Amazon Ads

incl. Amazon DSP

  • Interfaces5
  • TypesREST, MCP, Other, SDK
  • Exact tasks3 of 3
  • Last re-checked14 Nov 2026
  • Maturity index69 · rank 12

States are what public documentation describes for each interface, not account entitlement or tested behaviour. Dataset v2026-11-15.30. How the Atlas decides.

Open the full record Suggest a correction

  1. REST

    Campaign/creative management API

    GA · since 9 Jan 2025 (earliest dated source found)

    • Readdocumented
    • Writedocumented
    • Optimizedocumented
    • Activatedocumented
    Access
    Approved partners or by request
    Sign-in
    OAuth, API key or token
    Qualifies for
    Claims reviewed
    Not re-checked yet; research dated 12 Nov 2026 · 2 sources on the record
    Sources watched
    Weekly watch read 2 of 2 cited pages, last 13 Nov 2026
    Endpoint probed
    Not probed
    Task scope from
    Reviewed use-case tag only (objects not typed)
    In the Atlas since
    Release v2026-11-12-proto.1 (when we recorded it, not a launch date)

    Setup not mapped yet: start from the vendor's docs linked on the full record.

    Notes and sources Correct M006

  2. REST

    Sponsored Ads API

    GA

    • Readdocumented
    • Writedocumented
    • Optimizelimited
    • Activatelimited
    Access
    Approved partners or by request
    Sign-in
    not stated
    Qualifies for
    Claims reviewed
    Not re-checked yet; research dated 12 Nov 2026 · 1 source on the record
    Sources watched
    Weekly watch read 1 of 1 cited pages, last 13 Nov 2026
    Endpoint probed
    Not probed
    Task scope from
    Reviewed use-case tag only (objects not typed)
    In the Atlas since
    Release v2026-11-12-proto.1 (when we recorded it, not a launch date)

    Setup not mapped yet: start from the vendor's docs linked on the full record.

    Notes and sources Correct M100

  3. MCP

    Amazon Ads MCP Server

    Open beta · since 2 Feb 2026 (beta start)

    • Readdocumented
    • Writedocumented
    • Optimizelimited
    • Activatelimited
    Access
    Approved partners or by request
    Sign-in
    OAuth, API key or token
    Qualifies for
    Claims reviewed
    Re-checked 14 Nov 2026 · 4 sources on the record
    Sources watched
    Weekly watch read 2 of 4 cited pages, last 13 Nov 2026
    Endpoint probed
    Not probed
    Task scope from
    Typed objects or effects from the record
    Compared side by side
    Walled-garden ads MCP servers
    Evidence depth
    Each of read, write, optimize, activate, access, auth, launch is tied to one decisive vendor source, checked 14 Nov 2026. Sources and paraphrases on the full record.
    In the Atlas since
    Release v2026-11-12-proto.1 (when we recorded it, not a launch date)
    Set it up from the vendor's own pages, checked 14 Nov 2026
    Provider
    Amazon Ads (official, hosted)
    Hosting
    Hosted by Amazon Ads, one endpoint per region: NA below; EU https://advertising-ai-eu.amazon.com/mcp; FE https://advertising-ai-fe.amazon.com/mcp. The URLs are not region-agnostic.
    https://advertising-ai.amazon.com/mcp
    Before you start
    • A Login with Amazon (LwA) application and an Amazon Developer account with Amazon Ads API access, or the API onboarding steps first
    • An authorization grant that returns access and refresh tokens, unless you use the OAuth 2.1 browser login
    • Account context: by default the assistant asks which account to use (query_advertiser_accounts lists them); a fixed mode pins one account in headers
    Sign-in
    Headers Amazon-Ads-ClientId (your LwA client ID) and Authorization: Bearer <access token>. Alternatively OAuth 2.1, where the MCP client fetches tokens through a browser login and no token sits in the config.
    Clients
    • Kiro CLI: Add the entry below to ~/.kiro/settings/mcp.json with your client ID and access token, start kiro-cli and check /tools.
    • Claude, ChatGPT, Amazon Bedrock and AgentCore: Named by Amazon as MCP-compatible clients; use the endpoint for your region with the headers or OAuth 2.1.
    Config

    Kiro CLI, dynamic account context, from the Get Started page (source). Placeholders stay placeholders; it holds no credentials.

    {
      "mcpServers": {
        "amzn-ads-mcp": {
          "url": "https://advertising-ai.amazon.com/mcp",
          "headers": {
            "Authorization": "Bearer Atza|<your_access_token>",
            "Amazon-Ads-ClientId": "<your_client_id>",
            "Accept": "application/json, text/event-stream"
          },
          "timeout": 60000,
          "disabled": false
        }
      }
    }
    First read
    Documented prompt: "Can you give me the advertiser accounts that I have access to?" (tool account_management-query_advertiser_account). An account-data call under your own sign-in, read-only.
    Sandbox
    No sandbox or test environment is published.
    Cost
    No price stated for the standard tools; open beta for Amazon Ads partners with active API credentials. Expert tools such as AMC SQL generation have their own published beta and pay-per-use terms. Source
    Limits
    • Write tools include campaign creation, budget updates and deletes (e.g. delete_campaign, delete_ad); Amazon documents disabling tools through client filters
    • Fixed account mode: all headers must belong to one account; not every tool works at manager-account scope
    • The AMC SQL Generator expert tool is a closed beta

    This page is a directory lookup: nothing here signs in, installs, writes or spends. Access, approval and the states above are separate facts; a recipe never widens them.

    Notes and sources Correct M101

  4. REST

    Amazon Marketing Cloud APIs

    Released · no GA label · since 25 Oct 2023 (earliest dated source found)

    • Readdocumented
    • Writedocumented
    • Optimizeunknown
    • Activateunknown
    Access
    Approved partners or by request
    Sign-in
    OAuth
    Claims reviewed
    Re-checked 13 Nov 2026 · 6 sources on the record
    Sources watched
    Cited pages not on the weekly watch yet
    Endpoint probed
    Not probed
    Task scope from
    Typed objects or effects from the record
    In the Atlas since
    Release v2026-11-14.11 (when we recorded it, not a launch date)

    Setup not mapped yet: start from the vendor's docs linked on the full record.

    Notes and sources Correct N313

  5. Other, SDK

    Amazon Publisher Services Streaming TV C2S/S2S bid integrations and Vega APS client helper

    Released · no GA label

    • Readdocumented
    • Writeexcluded
    • Optimizeexcluded
    • Activateunknown
    Access
    Invite, waitlist, beta or staged rollout
    Sign-in
    not stated
    Claims reviewed
    Re-checked 13 Nov 2026 · 6 sources on the record
    Sources watched
    Cited pages not on the weekly watch yet
    Endpoint probed
    Not probed
    Task scope from
    Scope not mapped
    In the Atlas since
    Release v2026-11-14.11 (when we recorded it, not a launch date)

    Setup not mapped yet: start from the vendor's docs linked on the full record.

    Notes and sources Correct N314

Dated changes

  1. CorrectedAmazon Ads MCP Server: was Task scope from a reviewed use-case tag: qualifies for creating or changing a campaign only; now Write objects typed as campaign and budget: the MCP overview lists Update budget among the standard tools and documents raising a campaign budget, so it…
  2. Vendor announcement Amazon Ads MCP server open beta
  3. Vendor announcement Amazon DSP campaign and creative APIs generally available

Every change with its stable ID: changes.json · RSS.

Cite as: No Fluff Advisory, Agentic Ecosystem Atlas, Amazon Ads, dataset v2026-11-15.30, https://nofluffadvisory.com/agentic-atlas/companies/amazon-ads/