Skip to main content
Glama
amirmcs

Pega MCP Server

by amirmcs
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PEGA_BASE_URLYesThe URL of your Pega instance (e.g., https://your-pega-instance.example.com/prweb)
PEGA_CLIENT_IDYesOAuth2 Client ID for Pega authentication
PEGA_TOKEN_URLYesThe Pega OAuth2 token endpoint URL
PEGA_CLIENT_SECRETYesOAuth2 Client Secret for Pega authentication
PEGA_ENABLED_TOOLSNoComma-separated tool names to allowlist (e.g., pega.get_case,pega.get_case_actions)
PEGA_DISABLED_TOOLSNoComma-separated tool names to blocklist (e.g., pega.submit_case_action,pega.attach_document_to_case)
PEGA_CASES_API_BASE_PATHNoBase 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_VIEWNoData view used as a fallback for pega.get_cases when GET /cases is not supported (HTTP 405)D_pyMyWorkList

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

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