Pega MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Pega MCP Servershow me the details and available actions for case C-501"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
pega-mcp-server
Generic TypeScript MCP server for Pega case operations with definition-driven tool registration.
Purpose
This project provides an MCP tool layer for reading and mutating cases in a flexible way. Tool wiring is metadata-based, so adding tools does not require editing server registration logic.
Related MCP server: Operaton MCP
Supported MCP Tools
pega.get_casesInput: optional
limitReturns:
{ ok: true, data: { cases: [...] } }
pega.get_caseInput:
caseId, optionalviewType,pageName,originChannelReturns:
{ ok: true, data: { case: ... } }
pega.get_case_actionsInput:
caseId, optionaloriginChannelReturns:
{ ok: true, data: { actions: ... } }
pega.get_case_viewsInput:
caseId,viewId, optionaloriginChannelReturns:
{ ok: true, data: { view: ... } }
pega.attach_document_to_caseInput:
caseId,fileName,mimeType,fileContentBase64Returns:
{ ok: true, data: ... }
pega.submit_case_actionInput:
caseId,action, optionalcontentReturns:
{ ok: true, data: ... }
All tools return a standard failure format:
{
"ok": false,
"error": {
"code": "INVALID_INPUT | NOT_FOUND_OR_FORBIDDEN | INTERNAL_ERROR",
"message": "Human-readable explanation",
"suggestion": "Optional recovery guidance"
}
}Environment Variables
Required:
PEGA_BASE_URL(for examplehttps://your-pega-instance.example.com/prweb)PEGA_CLIENT_IDPEGA_CLIENT_SECRETPEGA_TOKEN_URL(for examplehttps://your-pega-instance.example.com/prweb/PRRestService/oauth2/v1/token)
Optional:
PEGA_CASES_API_BASE_PATH(default:/api/v1)Common v2 path when base URL includes
/prweb:/api/application/v2Some deployments use app context:
/PRAuth/app/work-manager/api/application/v2
PEGA_CASES_LIST_DATA_VIEW(default:D_pyMyWorkList)Used as a fallback for
pega.get_caseswhenGET /casesis not supported (HTTP 405)Endpoint shape:
POST <PEGA_CASES_API_BASE_PATH>/data_views/<dataViewId>
PEGA_ENABLED_TOOLScomma-separated tool names to allowlistExample:
pega.get_case,pega.get_case_actions
PEGA_DISABLED_TOOLScomma-separated tool names to blocklistExample:
pega.submit_case_action,pega.attach_document_to_case
Run Locally
npm install
cp .env.example .env
npm run devBuild
npm run build
npm startTest
npm testExample Outputs
pega.get_cases
{
"ok": true,
"data": {
"cases": [
{
"ID": "C-501",
"caseType": "Insurance Claim",
"status": "Pending Documents"
}
]
}
}pega.get_case
{
"ok": true,
"data": {
"case": {
"ID": "C-501",
"caseType": "Insurance Claim",
"status": "Pending Documents",
"uiResources": {
"root": {
"type": "page"
}
}
}
}
}Detailed request/response contracts:
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables agents to interact with Salesforce, Atlassian (Jira/Confluence), and Supabase through standardized tools and resources. Provides both read-only access for querying data and write operations for managing records across these enterprise platforms.1
- AlicenseBqualityBmaintenanceExposes over 300 Operaton BPM REST operations as tools for AI agents to interact with the Operaton engine. It enables managing process deployments, instances, user tasks, and decision tables through natural language commands.10024Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables interaction with Salesforce data and services via custom MCP tools, including account analytics, opportunity queries, case creation, and AI agent invocation.4
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to perform CRUD operations, query data, fetch schemas, and execute custom operations on Microsoft Dynamics 365 CRM entities.522MIT
Related MCP Connectors
SaaS intelligence for AI agents. 5 unified tools cover 1,000+ services with 91-96% token savings.
Gateway between LLM agents and world data through eight tools and a bundled endpoint catalog.
Runtime permission, approval, and audit layer for AI agent tool execution.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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