Plug your AI agent into your marketing stack

Our MCP server exposes 17 tools covering the live-artwork wallet card platform, the cards your customers carry in Apple and Google Wallet. Connect an MCP client with your store's key and your agent can:

• Push a promo offer to every installed wallet card
• Compose the offer image: wording, product photos, strike-through pricing
• Generate claim links and signup invites
• Sync loyalty points to cards
• Schedule pushes for later
• Read and update the card design
• Pull install counts, notification logs, and campaign stats
• Query budtender signup attribution

That is the entire push workflow (compose, preview, confirm, schedule, measure), operable by an agent in one conversation. To be equally clear about the boundary: email campaign control through MCP is not live yet. It is on the roadmap below, and until it ships, wallet operations are the honest extent of the claim.

Letting software agents touch real customers is exactly as dangerous as it sounds, so the server is built defensively from the first byte:

• Per-store keys, instantly revocable. Keys are stored hashed; the key is the scope. Rotate or kill an agent's access in one click.
• Confirm-gated writes. Any action that touches cards requires an explicit confirm flag. Without it, the agent receives a dry run showing the exact impact, down to the number of installed cards affected, and nothing executes.
• Tamper-evident audit trail. Every call, every dry run, every confirmed push is logged where you can review it.
• Rate limits. A misbehaving or looping agent hits a wall at 120 calls per minute, not your customer base.

This is the same discipline we apply to sending infrastructure on our deliverability stack: automation with brakes, so the system protects you from bad days and bad prompts alike.

Alpine IQ has invested genuinely in AI: an AI Sales Agent product (marked "NEW" in their navigation as of August 2026), AI Condition nodes inside Flows, AI-generated audiences, and an acquired AI budtender. Those are in-platform features: their AI, inside their dashboard, on their roadmap. What we ship is the opposite shape: an open MCP server that lets your agent, whichever one you already use, operate the platform from outside. Your tooling, your prompts, your workflows; our tools and guardrails.

The distinction matters because agent ecosystems are compounding fast. A platform with an open protocol surface rides every improvement in Claude or ChatGPT the day it ships; a closed AI feature improves when the vendor gets to it.

Klaviyo, Mailchimp, and the broader martech stack all have developer APIs, but an API is for engineers with weeks, not an operator with a sentence. MCP is the difference: a typed tool surface with previews and confirmations that a non-programmer can drive through a chat window. Mainstream platforms are only beginning to expose MCP surfaces, and none of them will underwrite a dispensary's use case anyway: the same cannabis-policy exposure that affects their sending affects their platform terms.

For AI-forward dispensary operators, the practical takeaway: this is the one marketing stack where "ask your agent to run tonight's push" is a live, logged, confirm-gated workflow today, included with wallet plans on our public pricing page, not an enterprise add-on.