Google Tag Manager

Forum Discussion

BradRossman's avatar
BradRossman
Supporter
3 months ago

Braze MCP Server - Prompts and Use Cases

Hey all, I was very excited to see the release of the Braze MCP server and set it up with Claude this morning. It's very impressive, so far I've gotten nice analytics reports for overall Canvas performance, but limited to 14 days at a time with the canvas data series analytics API, or to ask for the 'top performing Push campaigns for July 2025'. I wanted to hear some other prompts people were using to get reporting value quickly from Braze. 

I also was interested to pull in messaging templates (Email, IAM) and see how well it could add/edit liquid.

Disclaimer: Of course don't give the MCP API key more than read access while we play around with the functionality as we don't want it to go and edit anything in Prod! 

3 Replies

  • Just tested it and I like it. Really fast to set it all up. 14 days is a bummer since for some lifecycle campaigns you want to see across longer periods of time, but good indicator for some others. I tested prompts like: 1) Find underperforming canvases (low conversions, high sends), 2) Compare performance of my canvases over the last 14 days, which ones had the conversion rates? 

  • We wonder if Braze has any plans to expand the 14 day limitation for Canvas Analytics. They offer a longer timeframe for Campaigns!

  • We developed our own MCP for the Braze API a few months before Braze released their official MCP, and we ran into the same issues: the 14-day data availability limit, as well as challenges with context length when analyzing journeys that include many steps and messages (Braze API returns all the HTML to the AI, which significantly increases the amount of data it receives in context).

    When Braze launched their MCP, I was hoping they had already addressed these issues, but it seems they encountered the same challenges. In the end, we solved it with a custom development on our side.

    I also shared this feedback with Braze, and I really hope they reconsider this limitation, even though I assume it was originally introduced due to server performance and cost considerations on their side.