Working with Tap AI
Connect a compatible AI client to Tap's public buyer MCP server, select the acting organization, review approvals, protect data, and troubleshoot OAuth.
4 min readUpdated
Something missing from this page? Email help@tap.co
Tap exposes an authenticated buyer Model Context Protocol server at:
https://mcp.tap.co
A compatible AI client can use Tap's canonical buyer commands for identity, Campaigns, Brands, Products, radio and TV RFPs, DOOH planning and RFPs, directory research, response option comparison, private buy compositions, approved Order placement, memory, files, guide help, and related buyer work.
The client does not receive the Tap Agent runtime, shell, filesystem, supplier-only tools, email, Slack, Google Drive, or your Custom MCP connections.
In the AI client, add a remote MCP server using https://mcp.tap.co. If the client asks for a transport, choose Streamable HTTP.
The client should open a browser sign-in flow. Sign in with your Tap account and select the buyer organization that this connection should use. The connection receives only the standard identity scopes required by Tap.
One authorization operates in one selected buyer organization. To act in another organization, remove or disconnect the Tap authorization in the AI client and connect again, selecting the other organization.
Most reads and draft mutations can run inside the authenticated buyer organization. The following actions require a separate exact approval before execution:
A supporting client receives a structured approval request with the consequence and acting organization. Approve only when the shown command and input match your intent. Decline, cancel, expiry, input changes, or replay under another person or organization do not execute the action.
A client without structured form approval receives an approval-required result and a Tap review link. Complete the review there, then return to the client.
The server returns bounded text and structured results for the selected buyer organization. It never returns bearer tokens, cookies, session secrets, stack traces, or raw telemetry.
Operational diagnostics include only bounded client and command metadata, latency, result class, approval status, and rate-limit class. They do not include raw command inputs or results.
The client itself can retain prompts or tool results under its own policies. Review the AI client's data controls before connecting Tap, especially for commercially sensitive Campaigns, rates, contacts, and uploaded-file results.
For a Tap how-to question, the client should search the user guide, take the returned slug, and read the complete page before answering. The search excerpt is only a locator. Cite the page URL in the final answer.
The public Tap MCP server lets another AI client use Tap. The Custom MCP server option inside the Tap Agent does the reverse: it lets Tap connect to one remote server you configure. Custom-server credentials are encrypted, never added to chat, and every remote call requires approval.