Pega released Infinity AI Plugins on GitHub, built on the open-source Model Context Protocol (MCP). The repo documents official support for Claude Code, GitHub Copilot CLI, Codex, and opencode—but Windsurf isn’t currently listed as a supported client. Since Windsurf natively supports MCP hosts, we might be able to run these plugins directly inside the editor, meaning real-time conversation with your Pega runtime, property builds, and live view updates all without leaving the IDE.
Has anyone actually tested this in Windsurf yet?
If anyone has run this setup, please reply to share what you found—whether it worked, hit blockers, or led somewhere unexpected.
Although Windsurf/Devin Desktop is not currently called out as an officially documented client, it does support MCP servers and the Pega Infinity Authoring Plugin is built on a standards-based MCP architecture. Given that alignment, I would expect a good likelihood of compatibility. I haven’t seen a published validation yet, but I would be happy to test it this week and report our findings back to the group
Worth a try @garce let us know how it goes. MCP might work but we may have some hiccups w.r.t authorization. If 401 are returned then its likely that infinity plugin tool schemas are expecting short lived bearer tokens but windsurf mcp host doesnt. interested to know the findings @STEWJ
I’ve tried with GitHub Copilot CLI and able to interact with Pega Infinity studio with ease as shown below. I’ll try & explore Windsurf to see if it works!
This is clearly game changer for Pega AI-assisted development without logging Pega instance.
I was able to leverage the Pega AI Authoring plugin capability with Devin (Formerly WindSurf) . I ran Devin on the desktop locally, provided the github url and it brought in the MCP server allowed me to configure using the pega-setup command. It did go through a series of actions within Devin agent to make it work. Below is the result of it creating a decision table on my Infinity 26.1 instance.
