PivotPilotPivotPilot MCP
Connect compatible AI clients to PivotPilot so they can work with the same Amazon Ads data, analysis and controlled action capabilities available inside PivotPilot. Your AI client handles the conversation and the reasoning; PivotPilot remains the system of record for your data, your permissions, and any change that reaches Amazon.
This page is public information about PivotPilot MCP. The MCP server itself runs on the PivotPilot application domain, and connecting a client is done from inside PivotPilot under Settings → MCP, which shows your server address and walks through the rest.
What a connected client can do
Read
Inspect your synced Amazon Ads data and PivotPilot's analysis — campaigns, ad groups, keywords, targets, search terms and performance — together with the break-even and target thresholds you have set per product. PivotPilot works from data it has imported and normalized from Amazon, not from a live feed of the Amazon console.
Propose
Draft campaign changes. A proposal is recorded in PivotPilot and changes nothing on Amazon. This lets you keep a client fully useful for analysis and planning while it has no ability whatsoever to alter your account.
Approve
Applying a change to Amazon requires approval authority that you grant separately and explicitly. It is not included when you connect an app and is never granted automatically — a client that needs it has to request it, and you decide in a second, deliberate authorization. If you would rather keep approval in the product, you can simply never grant it, and approve in PivotPilot as usual.
Track and reverse
Every change is recorded with the app, the account and the request behind it, so you can see what a connected client did and when. Many of the supported change types can also be reversed from PivotPilot, which rebuilds the reversal from its own recorded baseline rather than letting a client describe one. Not every change type is reversible.
How permissions work
- A connection carries reading and proposing as its normal permissions. Approving changes is separate, explicit, and never automatic.
- A connected app can never do something you are not allowed to do. Your role, your execution permission, the Amazon profiles you can see and your organization's MCP access are re-checked on every single request — connecting does not freeze any of them.
- Access can be limited to selected Amazon profiles when a connection is authorized. Left unrestricted, access follows the profiles currently available to your organization and is re-checked live rather than fixed at the moment you connect.
- You can disconnect a connected app at any time from Settings → MCP. Disconnecting ends its access immediately.
Connecting and security
Compatible clients connect through browser-based authorization: the client sends you to PivotPilot, you review exactly what it is asking for on a consent screen, and you approve or decline. The client starts that flow itself — PivotPilot never reaches out to your client — and no long-lived key needs to be pasted anywhere.
For clients that cannot complete a browser authorization, PivotPilot still supports a personal token you create yourself and paste into the client. That path is available from Settings → MCP, and browser authorization is the recommended one where a client supports it.
Technical note. PivotPilot acts as both an OAuth 2.1 authorization server and the protected resource, with PKCE required on every authorization, standards based discovery so a client can configure itself, and refresh tokens that rotate on use. Access is bound to the PivotPilot MCP resource specifically, so a credential issued for it is not a general-purpose key to your account.
Client compatibility
Claude Code is verified against this deployment — tested end to end on version 2.1.234 on 2026-08-24, including discovery, browser authorization and reading live account data.
Other clients that support remote MCP servers over HTTP with browser authorization may also work, but they have not been verified here. Because client support for remote MCP servers changes quickly, check your own client's documentation for its current setup steps rather than relying on instructions copied from elsewhere.
Availability
MCP support is in early access. It is not currently part of the standard plan features, and it is not something a subscription change switches on — it is enabled per organization while we work with early users.
If you would like MCP enabled for your organization, email us at hello@pivotpilot.ai and we will take it from there.
Already have MCP access?
Sign in to PivotPilot and open Settings → MCP to copy your server address, connect a client, and manage or disconnect anything already connected.
New to PivotPilot? Sign in or read more about the product.