No-code path
Use guided setup first
Use guided defaults and keep sponsor delivery disabled for private tool-only contexts.
Solution setup
A safe sponsorship layer for MCP-adjacent products.
Use wavebird in the host surface around tool usage, not inside private context exchange between clients and tools.
Developer path
Keep control in your backend
Call wavebird from the host backend after the tool result is ready for display.
Trust boundary
What stays protected
The MCP context itself is not the ad payload. Keep sponsorship at the app surface boundary.
Implementation rule
Start in sandbox, then promote the same placement.
Use the Server Test Key while tuning placement and disclosure. Move to the Server Production Key only when payout details and partner readiness are complete. The request shape stays the same.