Architectural view of Connect MCP
Modern enterprise applications rarely operate in isolation. Business processes often depend on external services, such as compliance engines, fraud-detection platforms, knowledge repositories, enterprise search systems, industry-specific AI services, and third-party agent ecosystems. Integrating these services traditionally requires custom APIs, connectors, and specialized implementation.
As organizations adopt agentic AI solutions, Pega Agents might require information or functions from systems outside a Pega application. Instead of building a custom integration for each external service, Connect MCP provides a standardized connection between Pega and external systems that comply with the Model Context Protocol (MCP).
Connect MCP implements MCP consumption in Pega. A Pega Agent or workflow can connect to an external MCP server and call the tools that the server exposes. In this architecture, Pega acts as the MCP client, and the external system acts as the MCP server. Pega orchestrates the business process, while the external MCP tools provide specialized functions.
Consider an expense reimbursement application. A Pega Agent needs to determine whether an expense violates an organization’s policy. Instead of embedding the compliance logic in the application, the Agent calls an external compliance service through MCP. The service returns the result, and Pega continues processing the workflow.
Pega retains control of the business process, while the external MCP tool provides the specialized information or function that the process requires.
How Connect MCP works
A Connect MCP Rule connects Pega Platform™ to an external Model Context Protocol (MCP) server. After you configure the Rule, Pega Agents discover the tools that the server exposes and call the appropriate tools when needed.
A Connect MCP Rule is the MCP equivalent of an integration connector. Unlike connectors that consume REST operations or SOAP services, a Connect MCP Rule consumes tools that an external MCP server exposes.
The Connect MCP Rule is the primary configuration object for a Connect MCP integration. It:
- Defines the external MCP endpoint
- Stores authentication details
- Specifies transport configuration
- Enables tool discovery
- Allows Pega Agents to invoke external MCP tools
The rule supports MCP communication using Streamable HTTP and allows Pega Agents to consume tools that external MCP servers expose.
MCP Connect Step
While Pega Agents typically use Connect MCP rules, Pega Infinity™ also introduces the MCP Connect step.
The MCP Connect step lets a case workflow invoke an external MCP tool at a specific point during case processing without requiring a separate Pega Agent. As a result, the case lifecycle can include interactions with external MCP tools.
Examples
- A workflow could:
- Invoke an external fraud detection tool during claim processing
- Query an external policy service before issuing an approval
- Retrieve information from an enterprise knowledge system
- Call an external industry-specific AI service to enrich a decision
Infinity MCP architecture
Connect MCP enables Pega Infinity to use capabilities that external Model Context Protocol (MCP)-compliant systems expose. In this interaction pattern, a business process or agent in Pega Platform invokes an external MCP tool through a Connect MCP Rule. The external MCP server runs the requested capability and returns a structured response. Pega Platform uses this response to continue workflow processing, enrich decisions, or automate business actions.
The following diagram illustrates the flow of the Connect MCP:
Security and governance
Connect MCP follows the enterprise governance principles that apply across Pega.
Organizations manage authentication information by using Authentication Profiles to control how Pega accesses external MCP services. Through application configuration, organizations can specify different MCP endpoints and authentication settings for each environment.
Connect MCP keeps workflow governance within Pega. External MCP servers provide functions, but Pega continues to manage workflow orchestration, Case progression, decisions, and business outcomes.
LSA perspective about Connect MCP
Connect MCP provides a standard approach to enterprise integration.
For Lead System Architects (LSAs), Connect MCP introduces new architectural options. LSAs can integrate external AI services, knowledge systems, industry platforms, and specialized business tools into workflows while reducing dependencies on specific vendor implementations. Connect MCP provides a standard integration layer for AI-enabled services.
Architects must also define clear boundaries for business logic. Use Connect MCP to augment workflows, not to replace workflow orchestration in Pega applications. Keep enterprise policies, workflow orchestration, approvals, regulatory controls, and Case Management within Pega applications. Use MCP tools to provide specialized capabilities that enhance the workflow.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?