pega-dx

The Pega DX MCP Server exposes a conversational bridge between GenAI agents, IDEs, and MCP-enabled clients and Pega Infinity applications. It translates natural language interactions into Pega DX API calls, enabling tools to read cases, assignments, attachments, and related data, and to trigger actions within Pega Infinity. With 67 tools organized into 11 categories, you can selectively enable tool groups via environment variables to tailor capabilities for your environment. In MCP clients like Claude Code or Claude Desktop, you configure the server (using add-json or a file) so that your agent can request specific Pega operations using human-friendly prompts. This setup is designed for experimentation and prototyping, not production use, and it supports OAuth 2.1 with PKCE for secure access.

Prerequisites:

• Node.js 22+ and npm installed on your machine
• Access to a Pega Infinity environment with DX API enabled
• OAuth 2.1 client credentials (client_id and client_secret)

Installation steps:

1. Install the MCP server package globally:

# Install from npm
npm install -g @marco-looy/pega-dx-mcp

2. Ensure your Pega DX credentials and base URL are ready (PEGA_BASE_URL, PEGA_CLIENT_ID, PEGA_CLIENT_SECRET). You can start the MCP server directly with npx as shown in the configuration snippet or run via your MCP client using the provided command and environment variables.

3. Run the server (example using npx as configured in MCP):

# This will install and run the MCP server with your environment variables
# Or rely on your MCP client to supply the config

4. Connect from an MCP client:

• In Claude Code (recommended), add the MCP server with the following JSON payload:

{ "command": "npx", "args": ["-y", "@marco-looy/pega-dx-mcp"], "env": { "PEGA_BASE_URL": "https://your-pega-instance.com", "PEGA_CLIENT_ID": "your-client-id", "PEGA_CLIENT_SECRET": "your-client-secret", "PEGA_API_VERSION": "v2" } }

• Or for local development, run with Node directly from this project:

cd path/to/pega-dx-mcp
node src/index.js

5. Verify connectivity by confirming the MCP client can access the Pega DX tools and that the expected tool categories are loaded (adjust environment variables to enable/disable specific tool groups).

Tips and considerations:

• Use the provided environment variable controls to enable or disable tool categories (e.g., PEGA_CASE_TOOLS, PEGA_ATTACHMENT_TOOLS). All categories are enabled by default.
• Ensure your MCP client is restarted after adding or updating the MCP server configuration to load new tools.
• The server supports 67 tools across 11 categories; consider starting with the core case management tools and progressively enabling more categories.
• Store sensitive credentials securely (do not commit to source control). Consider using a secrets manager or MCP client-provided secret handling.
• If you encounter issues, verify the PEGA_BASE_URL and API version, and check the LOG_LEVEL (set to debug for troubleshooting).
• This MCP server is experimental; use in non-production environments and provide feedback to contributors.