This Hackathon showcases the latest capabilities in Pega Infinity ’26, including AI-assisted development, external AI agent connectivity, Constellation, high-fidelity Blueprinting, and AI-powered decisioning.
Choose the category that best matches your skills and ideas, then create a solution that demonstrates meaningful business impact, technical innovation, and the power of building with Pega.
You have until October 9 to submit your project—compete for awards and see your work recognized by our judges. Submit your project
Got questions? Ask them here, and a member of the team will get back to you.
Hi, Hackathon Trial instance for 2 members out of 3 is available under “My Trials” but for 3rd member It’s not showing up. Please help to resolve this. Let me know If I need to provide any other details to help resolve. Thank you!
@StephanieLouis Thank you for extending the submission deadline.
Our team had already submitted our hackathon files before the original deadline of October 9 21:00 UTC. We noticed that the submission portal currently does not provide an option to update or resubmit our files.
Could you please confirm whether resubmission/editing of existing submissions will be enabled for teams that would like to submit updated versions before the new deadline? Thanks in advance.
Hi Priya,
If you would like to resubmit you can send a Google Drive (or similar link) to me here via email and I can update the link to the files for our judges.
Thanks Stephanie, we did the same, invited and share link of Hackathon Instance. We are three members in team. But on the Trial instance it says 2 Members; I’m hoping that in actual registration all the three members are present .
Hi @StephanieLouis , Can you please enable MCP and A2A options for our instance. We are trying to do the use case for integrating with external agents.
Hi. I confirmed that the Community Edition instances support this configuration. Have you tried the instructions laid out in the documentation?
How MCP is configured (Pega as MCP server, so external agents can call Pega)
Step
What to do
1
In the authoring environment, go to Rules Library > Configuration > Configuration Settings Values.
2
Find the setting “(Experimental) Enable MCP” and set it to True. Merge or deploy the change.
3
The MCP endpoint then becomes available at {BASE_URL}/dx/api/application/v2/mcp.
4
Register an OAuth 2.0 client in the admin portal. Set Client Type to Public, Require PKCE to true and Grant type to Authorization code. Add the callback URLs of the external client, for example Claude Code or GitHub Copilot.
5
Optionally create a Service MCP rule to expose specific tools. The out-of-the-box pxCommon MCP service already includes tools such as pxSkillsTool, which reflect the application’s case types.
For the opposite direction, where a Pega agent calls tools on an external MCP server, you define a Connect MCP rule. This needs an Authentication Profile, and Application Settings can hold the target endpoint URLs.
@StephanieLouis I have shared the link of Google drive with our team’s latest demo video and presentation to your email. Kindly update this link for evaluation. Thanks