Pega MCP Server

Pega MCP Server

Enables interaction with Pega case operations through a metadata-driven tool layer, allowing users to fetch, update, and manage cases. It supports standard Pega actions such as retrieving case details, attaching documents, and submitting case actions via API.

Category
Visit Server

README

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.

Supported MCP Tools

  • pega.get_cases
    • Input: optional limit
    • Returns: { ok: true, data: { cases: [...] } }
  • pega.get_case
    • Input: caseId, optional viewType, pageName, originChannel
    • Returns: { ok: true, data: { case: ... } }
  • pega.get_case_actions
    • Input: caseId, optional originChannel
    • Returns: { ok: true, data: { actions: ... } }
  • pega.get_case_views
    • Input: caseId, viewId, optional originChannel
    • Returns: { ok: true, data: { view: ... } }
  • pega.attach_document_to_case
    • Input: caseId, fileName, mimeType, fileContentBase64
    • Returns: { ok: true, data: ... }
  • pega.submit_case_action
    • Input: caseId, action, optional content
    • Returns: { 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 example https://your-pega-instance.example.com/prweb)
  • PEGA_CLIENT_ID
  • PEGA_CLIENT_SECRET
  • PEGA_TOKEN_URL (for example https://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/v2
    • Some 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_cases when GET /cases is not supported (HTTP 405)
    • Endpoint shape: POST <PEGA_CASES_API_BASE_PATH>/data_views/<dataViewId>
  • PEGA_ENABLED_TOOLS comma-separated tool names to allowlist
    • Example: pega.get_case,pega.get_case_actions
  • PEGA_DISABLED_TOOLS comma-separated tool names to blocklist
    • Example: pega.submit_case_action,pega.attach_document_to_case

Run Locally

npm install
cp .env.example .env
npm run dev

Build

npm run build
npm start

Test

npm test

Example 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:

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured