The properties, workflows, and templates you manage in Template Manager don’t have to live behind a UI you click through by hand. Template Manager runs an MCP server, so any MCP-compatible tool (Claude, ChatGPT, Cursor, etc.) — can act on your portals and templates directly, in conversation.
What that actually means
Instead of opening the app to find a template, check its dependencies, and click deploy, you can ask: “deploy the lead-scoring bundle to the Acme portal” — and Claude calls the same API the app itself uses, with the same safety checks (dependency order, ID remapping, unresolved-reference warnings) applied underneath.
Unlike the HubSpot MCP, we work with your templates and bundles, not AI hallucinations. Ask Template Manager to deploy a new Content Asset and it’s going to check if you have a Content Bundle. Ask it to create a new HubSpot Deal and it’ll error out; we work at the schema and automation level, not the CRM level.
What you can do
- List, save, and update templates across your connected portals conversationally.
- Deploy templates and bundles — including dry runs — without leaving your AI tool of choice.
- Ask which workflows or segments reference a given property before you change or remove it.
- Trigger a portal sync and check its status without switching to a browser tab.