Exposing Pega capabilities through Service MCP

Service MCP provides a structured way for Pega Platform™ applications to expose selected tools and Case Types to external AI assistants. A Service MCP Rule generates a dedicated MCP endpoint that external clients use to access the selected features. 

External assistants connect to the endpoint, discover the exposed tools and Case Types, and invoke the appropriate feature. Pega Platform processes the request in the application and returns the result to the client. 

The architecture consists of the following components: 

• An external MCP client 
• A Service MCP endpoint 
• Exposed tools and Case Types 
• The Pega application that provides the requested business functionality 

The Service MCP architecture includes the following components: 

• Service MCP Rule: The central configuration object that enables Pega Platform to expose tools and Case Types to external AI assistants. The rule defines the service configuration, generates the MCP endpoint, and controls which tools and Case Types the service exposes. 
• MCP endpoint: The service endpoint URL that Pega Platform generates when you enable a Service MCP Rule. External MCP clients use this endpoint to connect to the application, discover the available features, and invoke them. 
• Tools: The features that a Service MCP Rule exposes. You select the tools that external agents can use to invoke approved business functionality through MCP. 
• Case Types: The Case Types that external AI assistants can access through the corresponding Case Type tools. 
• External MCP clients: Third-party AI assistants or agents that connect to the Service MCP endpoint. These clients discover and invoke the tools and Case Types that the Service MCP Rule exposes. 

Service MCP uses the following process: 

Tool discovery: An external AI assistant connects to the Service MCP endpoint and discovers the tools and Case Types that the Service MCP Rule exposes. 

Tool selection: The external AI assistant selects the appropriate tool or Case Type for the requested business action. The assistant can select only the features configured in the Service MCP Rule. 

Tool invocation: The external AI assistant invokes the selected tool through the Service MCP endpoint. Pega Platform processes the request by using the corresponding application feature. 

Response processing: Pega Platform returns the response after it completes the requested operation. Service MCP uses Streamable HTTP transport but does not support partial or incremental response streaming. 

pxCommon  is an out-of-the-box Service MCP Rule that Pega defines on @baseclass in the Pega-GenAI Ruleset. The Case Types configured in the application dynamically determine the tools exposed by pxCommon.  You can use these tools to initiate workflows, perform Assignments, query data, and interact with Pega Knowledge Agent™ in Pega Platform. 

Broad access to the tools and Case Types in an application can be provided through pxCommon. You can restrict external access to specific capabilities by creating a separate Service MCP Rule that exposes only the required tools or Case Types. 

For more information about these tools, see pxCommon MCP tools

On the Tools tab of a Service MCP Rule, select the tools that you want to make available to external agents. External AI assistants can invoke the selected tools through the Service MCP Rule. On the Case Types tab of a Service MCP Rule, select the Case Types that you want to make available to external agents. External AI assistants can access the selected Case Types through the Service MCP Rule. 

Service endpoint and connectivity 

Service MCP provides the connection details that external agents require to access the features exposed by a Service MCP Rule. When you enable the service, Pega Platform displays the endpoint URL, transport type, authentication type, and service version. 

• Endpoint URL: Pega Platform generates a service endpoint URL when you enable a Service MCP Rule. Use this URL to configure the external agent. 
• Streamable HTTP transport: Service MCP uses Streamable HTTP transport. MCP returns a tool response only after Pega Platform completes the requested operation. Service MCP does not support partial or incremental response streaming. 
• Client connectivity: External agents connect to the Service MCP endpoint by using the configuration that the Service MCP Rule provides. The Configure Clients section provides connection guidance for supported client applications. 

Authentication and security 

Service MCP displays authentication details as part of the service configuration. When you enable a Service MCP Rule, Pega Platform displays the authentication type associated with the endpoint. 

• OAuth authentication: Service MCP supports Pega recommends OAuth 2.0 authorization code as the preferred authentication method. For improved security, use OAuth 2.0 authentication with an authorization code. Service MCP supports client credentials only when you map an Operator ID. 
• Authorization: In the Configure Clients section, select an OAuth 2.0 Client. Service MCP uses the selected client registration to generate the Connection Configuration for the external client application. 
• Least-privilege access: The out-of-the-box pxCommon Service MCP Rule provides access to all tools and Case Types in an application. To restrict access, create a separate Service MCP Rule and expose only the required tools or Case Types. 
• Data protection: The Connection Configuration section provides guidance for configuring client applications. The application does not save client credentials in the Service MCP Rule. 

Client configuration 

The Configure Clients section provides guidance for configuring applications that connect to a Service MCP Rule. Select a client application to review the generated Connection Configuration. 

• OAuth client registration: In the Configure Clients section, select an OAuth 2.0 Client for the client application. Pega Platform uses the selected registration to generate the Connection Configuration. 
• Connection Configuration: The Connection Configuration section displays a code snippet that contains the details required by the selected client application. 
• Third-party MCP clients: The client applications listed in the Configure Clients section are examples. A Service MCP Rule can also connect to applications that the Configure Clients section does not list. 

When you enable a Service MCP Rule, Pega Platform displays the service version in the MCP service details. The MCP service version is independent of the application version. Update the service version manually when required.

Check your knowledge with the following interaction: