Connect VS Code to Pega (For Windows Users)

Purpose: This guide sets up a Windows machine for Pega development in VS Code, including Git, Java, Node/NPM, GitHub Copilot, and the Pega Infinity Authoring or MCP connection workflow.

Software You Need

Step-by-Step Installation

Step 1: Open PowerShell as Administrator

Use Windows PowerShell or Windows Terminal. Running as administrator helps Winget install system-wide tools cleanly.

Step 2: Confirm Winget is available

Winget is the Windows Package Manager. Most modern Windows 10/11 machines include it.

winget --version

Step 3: Install Visual Studio Code

Install VS Code and then restart PowerShell so the code command is available on PATH.

winget install Microsoft.VisualStudioCode
code --version

Step 4: Install Git

Install Git and verify that the version is available from PowerShell.

winget install Git.Git
git --version

Step 5: Install Java 17

Install the Temurin JDK 17 distribution and confirm Java is available.

winget install EclipseAdoptium.Temurin.17.JDK
java -version

Step 6: Install Node.js LTS and verify NPM

Node.js includes NPM. This is needed for Constellation DX Component development and React-based tooling.

winget install OpenJS.NodeJS.LTS
node --version
npm --version

Step 7: Install GitHub Copilot in VS Code (might need authorization)

Pega employees: Sailpoint request for role: GitHub Enterprise - Copilot

Install Copilot and Copilot Chat from the command line. Then open VS Code and sign in with GitHub.

code --install-extension GitHub.copilot
code --install-extension GitHub.copilot-chat
code

Step 8: Clone the Pega MCP repository, if using local Agentic Authoring

Pega Employees: Sailpoint request for role: Github-Pega-GenAIEngineering-GenAI-Read **
**
Use this when your setup requires a local Infinity Rules MCP repository.

git clone https://github.com/Pega-EngineeringSandbox/infinity-rules-mcp.git
cd infinity-rules-mcp
code .

Step 9: Install the Pega Infinity Authoring plugin, if using Copilot plugin marketplace

Optional: Create a separate folder on your local drive, set it as the workspace folder in VSCode.

Use these commands when the Copilot CLI/plugin marketplace is available in your environment.

copilot plugin marketplace add GitHub - pegasystems/infinity-ai-plugins: infinity-ai-plugins · GitHub
copilot plugin install pega-infinity-authoring@Pega

Step 10: Configure the Pega connection in VS Code

After the plugin is installed, start a new session and ask the assistant to run pega-setup.

In VS Code, open Command Palette with Ctrl + Shift + P and run: Pega Infinity Authoring: Configure Connection. Enter the Pega base URL, OAuth client ID if required, and whether write operations should be enabled.

Note: When you try to connect to the instance of your choice you should see a browser pop asking you to login. Once logged in VSCode should be able to connect to your instance via MCP.

Step 11: Create or update the MCP configuration file

For VS Code-based MCP setup, create this file under your project folder: .vscode\mcp.json. Paste the MCP server JSON provided by your Pega environment or MCP Service rule.

OR ask the agent to create one for you.

Step 12: Start the MCP server and authenticate

Start the server from the VS Code extension or from the Start action above the MCP server entry. When the browser opens, authenticate with your Pega credentials.

Validation Commands

Run these checks after installation. If a command is not recognized, restart PowerShell or reboot Windows and try again.

code --version
git --version
java -version
node --version
npm --version

Connectivity Test Prompts

After the MCP server is started and authentication is complete, open a new Copilot Chat session in VS Code and try one of these prompts:

Check my Pega connection
Get details of my application

Quick Troubleshooting

Notes and Assumptions

· Use PowerShell as Administrator for Winget installs.

· Use Java 17 or later for Infinity Build / MCP server components.

· Use Node.js LTS when building Constellation DX Components or working with React-based UI assets.

· The exact MCP JSON depends on your target Pega environment, application, and OAuth configuration.

2 Likes