Skip to content

About

infinity-ai-plugins

Resources

Contributing

Security policy

Stars

21 stars

Watchers

2 watching

Forks

Repository files navigation

Pega Infinity Authoring plugins

Pega Infinity Authoring plugins connect development environments to Pega MCP, enabling you to build Pega applications from a development environment of your choice. By making internal assets available to external tools and agents, Pega is evolving its low-code approach to make application development more automated and accessible to users with different tool preferences.

The repository contains client-specific plugin payloads, marketplace layouts, and checked-in run-time artifacts and skills for producing installable packages.

Contents

Prerequisites

  • Node.js 22.14 or newer (Claude Code, Copilot CLI and Codex plugins). Check with node --version.
  • Java 17 or newer.

Since plugin version 0.2.1, the plugins start the MCP server with npx. On first use it downloads the server and skills (about 40 MB) from this repository's GitHub release, verifies their SHA-256 hashes, and caches them in ~/.infinity-rules-mcp/. Later starts use the cache. Access to npm and GitHub is needed on first use only.

If your client times out on the first start, download ahead of time:

npx -y --package=@pega/infinity-authoring-plugin@0.2.1 infinity-authoring-plugin prefetch

Without Node.js

Plugin versions before 0.2.1 bundled the server and keep working as installed, but updating moves you to the Node.js-based launcher. To keep running with Java only:

  1. Download infinity-rules-mcp-<version>.jar and infinity-skills-<version>.zip from the releases page, check them against the .sha256 files, and unzip the skills into a folder.

  2. Register the server in your client with java -jar <path/to/jar> --spring.profiles.active=stdio and the environment variable PEGA_SKILLS_PATH set to the skills folder. For example, in Claude Code:

    claude mcp add pega-infinity-authoring --env PEGA_SKILLS_PATH=/path/to/skills -- java -jar /path/to/infinity-rules-mcp-<version>.jar --spring.profiles.active=stdio
    
  3. Copy the pega-setup and pega-assistant skills from this repository into your agent's skills directory.

Supported Pega Infinity versions

Installing the plugin from the marketplace

Use this repository as the source when you install a marketplace from a Git path. The following table lists marketplace plugins and commands:

Agent CLI command
Claude Code claude plugin marketplace add https://github.com/pegasystems/infinity-ai-plugins.git
claude plugin install pega-infinity-authoring@Pega
GitHub Copilot CLI copilot plugin marketplace add https://github.com/pegasystems/infinity-ai-plugins.git
copilot plugin install pega-infinity-authoring@Pega
* Restart Copilot CLI for the plugin changes to take effect
Codex codex plugin marketplace add https://github.com/pegasystems/infinity-ai-plugins.git
codex plugin add pega-infinity-authoring@Pega
Alternatively, launch codex, type /plugins, navigate to Pega, and install Pega Infinity Authoring

Alternatively, you can use SSH Git URLs such as git@github.com:pegasystems/infinity-ai-plugins.git.

Setting up the plugin manually

Clone the repository, and then configure the MCP server and skills manually. The following table lists setup instructions for clients without a marketplace plugin:

Agent Setup instructions
Devin Download the MCP server and skills from the release page, configure the server in Devin's MCP metadata, and copy the shared Pega skills into a Devin skill directory. See Devin setup instructions.
opencode Merge the mcp block from plugins/pega/infinity-ai-plugins/opencode/opencode.json into opencode.json. Download the MCP server JAR and skills from the release page and set their absolute paths in the config. Copy plugins/pega/infinity-ai-plugins/opencode/skills/ into .opencode/skills/ in your project. See opencode setup instructions.

Setting up the plugin after installation

Claude Code, GitHub Copilot CLI, and Codex plugins include a built-in pega-setup skill for first-time configuration and troubleshooting.

Devin and opencode users can install the same shared skills by following the Devin setup instructions and opencode setup instructions.

After installing a marketplace plugin or completing manual setup, start a new session and ask the assistant to run pega-setup.

The pega-setup skill:

  • Checks whether the plugin run time is available and whether the client can connect to Pega Infinity
  • Guides the user through setting up the Pega Infinity base URL, optional OAuth client ID, and write access
  • Verifies the connection after configuration

When setting pega_base_url, use the environment root URL only. Do not include /prweb or any other path segment.

Updating marketplace installations

When this repository publishes a new plugin build, refresh the installed plugin from the marketplace. The following table lists the update commands:

Agent Update steps
Claude Code Run claude plugin marketplace update Pega to refresh the marketplace catalog.
Then run claude plugin update pega-infinity-authoring@Pega to update the installed plugin.
Run /reload-plugins or start a new Claude session afterward.
GitHub Copilot CLI Run copilot plugin marketplace update Pega to refresh the marketplace catalog.
Then run copilot plugin update pega-infinity-authoring@Pega to update the installed plugin.
Quit and reopen Copilot CLI afterward.
Codex Run codex plugin marketplace upgrade Pega to refresh the marketplace catalog.
Then run codex plugin add pega-infinity-authoring@Pega to refresh the installed plugin, or use the /plugins browser to reinstall it from Pega.
Start a new Codex session afterward.

Updating manual installations

To update a manual installation, follow these steps:

Agent Update steps
Devin Download the newer JAR and skills ZIP from the latest release, update the paths in Devin's MCP config, and start a new Devin session. Recopy the shared Pega skills if they changed. See Devin setup instructions.
opencode Download the newer JAR and skills ZIP from the latest release, update the paths in opencode.json, and restart opencode.

Tip

If adding the marketplace or cloning this repository fails with a "Filename too long" error, enable Git long-path support:

git config --system core.longpaths true

Overriding local skills

To test local infinity-skills with Claude Code, GitHub Copilot CLI, or Codex, set the pega_skills_path entry to the parent directory that contains the version directories. Set the entry in ~/.infinity-rules-mcp/config.json or %USERPROFILE%\.infinity-rules-mcp\config.json before you start the client.

{
  "pega_base_url": "https://example.pega.example.com",
  "pega_skills_path": "/path/to/infinity-skills"
}

Point pega_skills_path at the parent directory that contains the selected version directory, and set pega_infinity_version to the matching directory name.

If pega_skills_path is missing or empty, the plugin uses the skills it downloaded and cached.

Documentation

For more information, see:

About

infinity-ai-plugins

Resources

Contributing

Security policy

Stars

21 stars

Watchers

2 watching

Forks

Releases

Packages

Used by

Contributors