Building with Badge just got a lot easier. Designing passes, configuring geolocation, drafting push notifications, issuing passes at scale, and tracking activation status; these tasks have always required technical resources or multiple steps across the platform.
Today, that changes. Badge is excited to introduce the Badge MCP Server (beta), giving your AI tools direct access to your Badge workspace through natural language.
If you can describe what you want, you can build it, send it, or measure it. Whether you're setting up a new loyalty pass template, launching a push to a specific audience, issuing linked passes for a new cohort, or checking on activation rates, it's now possible through a simple conversation.
Setting up your Badge MCP Server
The Badge MCP Server connects AI clients like Claude Desktop, Cursor, and Claude Code directly to your Badge workspace via the Badge API.
To get started:
Choose your AI agent: Claude, ChatGPT, Gemini or any MCP compatible agent
Follow a few simple steps to connect the MCP server
Start building
What you can do with the Badge MCP Server
Here are the four areas where the MCP server makes the biggest difference, with real examples of what you can ask.
Pass Creation
Designing a pass used to mean navigating template configurations, defining field values, uploading assets, and setting up location triggers one at a time or programatically. Now you can describe what you want and let the AI do the heavy lifting.
Example prompts:
"Create a loyalty pass template with our brand colors, this logo (URL), a points balance field, name field, and available rewards field. Add a QR code tied to the member_id for in store identification."
"Update the back-of-pass with a link to our new Members Only Sweepstakes and prompt customers to enter. Here is the URL."
"Set up geolocation messages for our store locations in CA, NV, CO, and NY. The message should say, Members only perks are available today! Scan your pass to unlock benefits."
Pass Activation
Getting passes into the hands of members is often where programs stall. The MCP server makes it easy to issue passes in bulk, create linked passes for individual members, and organize passes into groups, all while keeping your data secure.
Example prompts:
"Create passes for the members in /Users/reference_desktop_file using the BRAND NAME loyalty template.
"Show me all passes created in the last week that haven't been added to a wallet yet. I will follow up with them via email"
"Create linked passes for the members in /Users/reference_desktop_file using the BRAND NAME loyalty template as the Parent Pass. Pass Template B is the template to use for the Linked Pass."
Engagement
Push notifications are Badge's highest-value channel, but drafting copy, selecting the right audience, and triggering sends has always required multiple steps. The MCP server brings that into a single conversation.
Example prompts:
"Draft three push notification messages for our spring sale. Keep them under 100 characters and make them feel urgent but not spammy. This is for my west coast audience"
"Send a push to all passes that were created more than 60 days ago. Use the message: New Benefits have been added since you joined! Details on the back of pass”
"Let’s send a first time offer to all members who have had passes created within the last 30 days. Use the message: We’re happy you joined the Tribe. New Member Rewards are available in your account. Details on the back of pass.”
Reporting
Understanding how your program is performing should not require a data team or the need to log into another platform. The MCP server gives you instant access to pass details, activation status, and campaign performance through plain English questions.
Example prompts:
"How many passes have been activated in the last 30 days, broken down by template?"
"Which passes were issued but never added to a wallet? Give me a count and flag the templates with the lowest activation rates."
“Provide me with the total number of link clicks in the last 30 days”
Tips for getting the most out of the Badge MCP Server
Start with a question, end with an action. Ask your agent to surface an insight first, then use that same conversation to act on it. "Which activated passes haven't clicked any back of pass links?" followed by "Draft a re-engagement push for that group" is more powerful than treating each step as a separate task.
Be specific. "Passes created in October for the BlackFriday Event template" will return far better results than "recent passes." Include template names, date ranges, and campaign names wherever you can.
Review before you send. Your agent will execute actions directly in your workspace. Before running bulk operations, always confirm how your inputs translate into the UI.
Think in workflows, not one-off prompts. The MCP is most powerful when you chain steps together in a single conversation: design the pass, configure the locations, draft the push, check the audience, send. Each step builds on the last.
Verify outputs before scaling. Before running bulk operations in production, use a test template or a small audience group to confirm the output looks right. The MCP moves fast, and it's easier to verify on 10 passes than 10,000.
Join the beta
The Badge MCP Server is available now in beta. To get started, contact your CSM.
Questions or feedback? Reach out to your Badge customer success contact or email [email protected]