Bulk template management via API (and ideally MCP)

Feature Ideas
1

The problem that keeps biting us: once your library grows past a few dozen templates, you can't reliably find every place a given piece of text lives. The same price, disclaimer, policy, or claim gets worded a dozen different ways across templates, so a plain search never surfaces all of them. When something changes, you're left opening templates one by one, hoping you didn't miss one.That's not just tedious, it's a real accuracy and compliance risk.

A single template still showing an old price, an outdated disclaimer, or a stale claim can go out to a customer before anyone notices, and right now there's no way to audit the whole library at once, let alone fix it in bulk.The core issue: there's no way to touch templates at scale outside the UI, and no good path for creating large batches of new ones either.

This bites in a lot of common situations:

  • Finding + fixing scattered text: a price, product name, disclaimer, or claim changes, and it's phrased inconsistently across dozens or hundreds of templates. Exact-match search misses them; an API/AI pass could actually find them all.
  • Bulk updates: even once you've found them, editing every affected template by hand is hours of work.
  • Fixing early setup mistakes: if templates hardcoded a value instead of pulling from a shared snippet, retrofitting them one by one is brutal.
  • Standing up net-new template sets at scale: launching a product, onboarding a team, or building a new folder of replies from scratch means creating everything manually, even when the raw material already exists somewhere.

That last one is where an API/MCP gets really powerful. Instead of writing net-new templates by hand, you could pull existing content from another source (say, exporting a team's best past replies from a help desk or CRM via its own MCP), have an AI tool reshape and standardize them, and push the finished set straight into Blaze as ready-to-use templates. Same idea for generating a full launch or onboarding set from a brief and dropping it in programmatically. It turns "build 50 new templates" from a week of manual work into a single pipeline.

The ask: a way to create, read, update, and delete templates programmatically. A REST API covers most of this. An MCP server on top would be the dream, since it'd let people connect their library to AI tools like Claude and to other MCPs, but even a plain bulk-edit/bulk-create API would be a massive win on its own.

I searched and didn't find an existing request for this. Happy to help test if it ever gets picked up.

If you'd use bulk/API template editing, upvote so it gets on the radar. Curious how big everyone's library is too, drop a number below.

2

Hi @Chris_Gutierrez, welcome back to the forum.

Thanks so much for sharing your feedback with us. Did you give a try using Data Blaze to store your dynamic data, like prices, product names, claim changes, or anything like that, and use our DB command to retrieve that data dynamically in each snippet, rather than having to edit them every time you have a data change?

If not, please give it a try, and let me know if you still have more use cases that you cannot achieve with Data Blaze.

3

Hey, just to clarify, the pricing example was really just an illustration, not the heart of the request. Data Blaze is cool for dynamic data substitution, but that's honestly a pretty different problem than what I'm describing here.

The real ask is twofold:

1. Creating templates programmatically -being able to spin up large sets of templates from external sources, pipelines, or AI-generated content without touching the UI one by one. Think pulling structured content from a CRM or help desk, processing it, and pushing it straight into Blaze as finished templates.

2. Analyzing existing templates via AI through MCP- connecting Blaze's template library to external AI tools (like Claude) and workflows so you can do things like audit the whole library, detect inconsistencies, identify gaps, or run bulk transformations using external logic and skills.

This is really about interoperability.. being able to plug Blaze into modern AI-native workflows and toolchains, not just swap out variables inside individual snippets. An MCP server sitting on top of a CRUD API would unlock a totally different category of use cases that dynamic data commands just don't touch.

4

Hi @Chris_Gutierrez

Thanks for clarifying your use cases. We'll look into it and see if there's a chance to implement something like this in the near future.

Thanks again for sharing your valuable suggestions with us.