What is the Model Context Protocol (MCP)?

We are named after it, and the name is no moat: Amazon and other advertising platforms already expose MCP capabilities, and an MCP server alone differentiates nothing. What is unusual here is that the agent transport and the browser exercise the same REST routes, the same tenant boundary, the same spending checks and the same approval records, so there is no second execution path with weaker rules. The stronger guarantee is what is absent: no agent tool exists for 11 consequential operations, including approval resolution, mandate revocation and issuing a spend grant. An agent can prepare and propose a plan, and a named person has to approve any spend. AdBuyMCP runs the hosted server. Joining the waitlist takes a short form and no card. James is setting the first customers up himself, so he reads every entry and comes back to you, and nothing is bought until the plan, the ads and the start date are confirmed with you. A compatible MCP client connects through Supabase OAuth, workspace selection and consent once workspace access, the client's own identity and its exact callbacks are approved. Its tools follow that workspace's enabled capabilities. There is no public connector or registry listing.