Pega MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PEGA_BASE_URL | Yes | The URL of your Pega instance (e.g., https://your-pega-instance.example.com/prweb) | |
| PEGA_CLIENT_ID | Yes | OAuth2 Client ID for Pega authentication | |
| PEGA_TOKEN_URL | Yes | The Pega OAuth2 token endpoint URL | |
| PEGA_CLIENT_SECRET | Yes | OAuth2 Client Secret for Pega authentication | |
| PEGA_ENABLED_TOOLS | No | Comma-separated tool names to allowlist (e.g., pega.get_case,pega.get_case_actions) | |
| PEGA_DISABLED_TOOLS | No | Comma-separated tool names to blocklist (e.g., pega.submit_case_action,pega.attach_document_to_case) | |
| PEGA_CASES_API_BASE_PATH | No | Base path for the Pega Cases API. Common v2 path: /api/application/v2. Some deployments use: /PRAuth/app/work-manager/api/application/v2 | /api/v1 |
| PEGA_CASES_LIST_DATA_VIEW | No | Data view used as a fallback for pega.get_cases when GET /cases is not supported (HTTP 405) | D_pyMyWorkList |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pega.get_casesB | Use this tool to list cases. Optional input: limit. Returns: { ok: true, data: { cases: [...] } } on success. Standard failure format: { ok: false, error: { code, message, suggestion? } }. |
| pega.get_caseA | Use this tool to fetch one case by identifier. Required input: caseId. Optional inputs: viewType, pageName, originChannel. Constraint: pageName requires viewType. Returns: { ok: true, data: { case: } } on success. Standard failure format: { ok: false, error: { code, message, suggestion? } }. |
| pega.get_case_actionsA | Use this tool to discover available actions for a case or fetch a specific action definition. Required input: caseId. Optional inputs: actionId, viewType, excludeAdditionalActions, originChannel. Returns: { ok: true, data: { actions: } } on success. Standard failure format: { ok: false, error: { code, message, suggestion? } }. |
| pega.get_case_viewsA | Use this tool to retrieve metadata for a specific case view. Required inputs: caseId, viewId. Optional input: originChannel. Returns: { ok: true, data: { view: } } on success. Standard failure format: { ok: false, error: { code, message, suggestion? } }. |
| pega.attach_document_to_caseA | Use this tool to attach files or URLs to an existing case. Required input: caseId. Attachment input mode 1: attachments array payload. Attachment input mode 2: fileName + fileContentBase64 (optional mimeType) for upload-then-attach flow. Returns: { ok: true, data: } on success. Standard failure format: { ok: false, error: { code, message, suggestion? } }. |
| pega.submit_case_actionB | Use this tool to execute an action on an existing case. Required inputs: caseId, action. Optional inputs: content, pageInstructions, attachments, eTag, viewType, pageName, originChannel. Returns: { ok: true, data: } on success. Standard failure format: { ok: false, error: { code, message, suggestion? } }. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/amirmcs/Pega-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server