Connect Tap to an AI client

What the Tap MCP server does

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, Plans, Brands, Products, radio and TV RFPs, DOOH planning and RFPs, directory research, Avail comparison, 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.

Add the server

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.

Understand approvals

Most reads and draft mutations can run inside the authenticated buyer organization. The following actions require a separate exact approval before execution:

• permanently deleting Brands;
• forgetting a saved memory;
• sending or resending a broadcast RFP;
• changing a live broadcast RFP deadline;
• adding a recipient to a live broadcast RFP;
• closing a broadcast RFP Exchange;
• sending a DOOH RFP.

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.

Know what data crosses the connection

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 Plans, rates, contacts, and uploaded-file results.

Use guide commands correctly

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.

Troubleshoot a connection

• The client cannot discover OAuth metadata: use the exact HTTPS server URL and remove any path added by the client.
• Sign-in succeeds but commands are unauthorized: disconnect and authorize again. Confirm that you selected an active buyer organization.
• No organization can be selected: your account needs an active agency or client-brand membership.
• The wrong workspace appears: reconnect and select the correct organization. One connection cannot switch organizations in place.
• Approval expired: rerun the exact command and review the newly issued request. Approval state expires after ten minutes.
• Rate limited: wait for the current minute window and reduce repeated polling. Read, mutation, and open-web research commands have separate limits.
• A tool is missing: refresh the client command catalog. Tap exposes only explicitly classified buyer commands.
• The client has no inline Tap card: the structured and text result is still complete. Inline review is optional client presentation.

Public Tap MCP versus Custom MCP

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.

Related guides

• Work with the Tap Agent
• Plan and send a DOOH RFP
• Manage buyer settings