The agent and the MCP server, answered in full.

No. What exists is a server you deploy yourself, single-tenant, behind a bearer token or your own tunnel. Public multi-tenant MCP needs an OAuth 2.1 authorisation server issuing per-user, per-organisation, audience-bound tokens, and the package deliberately does not embed one — that is an open gate rather than a setting. The setup instructions below are for a deployment you control.

A feature, and the site is named after it because it is the feature that changes how the product is used rather than the one that makes it defensible. MCP is an integration surface — Amazon and other advertising platforms already expose one — so an MCP server alone is not a moat. What is unusual here is that the agent transport and the browser are the same execution path, so pointing an agent at a media budget does not mean accepting a weaker set of rules than a person would get.

No, and the block is structural rather than a permission you remember to switch off. Consequential calls fail closed unless the incoming request matches an approval a human granted for those exact bytes, spend runs against a mandate with an explicit money ceiling and expiry, and enabling spend on a live line is a separately granted action that approval alone cannot perform. Agents cannot revoke or replace authority, close missions, or resolve human approvals.

The run stops. An ambiguous outcome raises an exception that requires an explicit human resolution before the run resumes, and it is never blindly retried. That is the specific failure this design exists to prevent: an agent that cannot read a supplier's response and tries again has just created a second campaign it does not know about.

The modern 2026-07-28 protocol over both streamable HTTP and stdio, with server/discover negotiation and per-request metadata. The pre-2026 initialize handshake also works over stdio and stateless HTTP, and the compatibility path is pinned by tests rather than assumed — including a 2025-03-26 HTTP round trip and cancellation behaviour in both eras.

Yes. It is a standard MCP server over stdio and streamable HTTP, so any MCP-compatible client can drive it. The setup instructions name Claude Code, Claude Desktop and claude.ai because those are the clients most people have, not because the server knows the difference.