MCP Agent Support in Pega Blueprint
One of the latest and interesting capabilities in Pega Blueprint is MCP Agent support.
With this update, workflows designed in Blueprint can be exposed through Model Context Protocol (MCP). This means AI assistants such as Claude can discover these workflows and interact with them using natural language.
Demo : https://youtu.be/LkXL4Xym3Dc?si=hL8s5WWGQVEKHh1e
This is important because Blueprint is usually the starting point for designing application workflows, case types, data models, and business processes. With MCP support, these designs can become more interactive at an earlier stage. Instead of only reviewing the workflow visually inside Blueprint, an AI assistant can understand what workflows are available and help users interact with them conversationally.
For example, a user could ask an AI assistant to explore a Blueprint workflow, understand the process steps, or interact with the available MCP-enabled actions. This creates a bridge between design-time workflow modeling and AI-assisted interaction.
It also shows how enterprise application design is moving toward a more connected and intelligent experience. Blueprint workflows are no longer just static design outputs. They can become accessible building blocks that AI assistants can discover and use.
This is a strong starting point for making Blueprint workflows more interactive even before they are imported into a full Pega application. The next exciting step will be seeing how these Blueprint designs evolve when they are imported, extended, and implemented within actual Pega applications.
Overall, MCP Agent support in Pega Blueprint is a promising step toward AI-assisted application design, connected workflows, and more dynamic enterprise automation.