Posts

Stop treating MCP, RAG, and Skills like alternatives.

Image
The confusion stems from the fact that all three "give AI capabilities." But in reality, they solve three completely different parts of the architecture: Data Access , Context Retrieval , and Action Execution . Here’s a breakdown of how it works: 1️⃣ MCP Connection (Real-Time Data) Before making any decision, the AI connects via Model Context Protocol (MCP) to fetch live data from internal databases, custom APIs, or CRM systems (like Pega). 2️⃣ RAG Knowledge Base (Context & Rules) The agent uses Retrieval-Augmented Generation (RAG) to pull company policies, legal regulations, and standard operating procedures (SOPs). This grounds the AI in enterprise context so it doesn't hallucinate. 3️⃣ Skills Execution (Automated Actions) Once the AI synthesizes live data + policy guidelines to make a decision, it triggers concrete Skills —such as updating case statuses, routing tickets, or dispatching real-time email notifications. 💡 Key Takeaway: AI Agents aren't...

My First YOLO Object Detection Experiment using Python with Multiple Images

Image
I recently tried a simple YOLO (You Only Look Once) object detection exercise using Python and the Ultralytics YOLO11 model. The goal was straightforward: instead of processing just one image, I wanted to provide multiple images , run object detection on all of them, and generate a single combined output image . What I Used Python Ultralytics YOLO YOLO11n pretrained model PIL/Pillow for image processing Multiple JPG images The Basic Approach First, I loaded the pretrained YOLO11 model: from ultralytics import YOLO model = YOLO("yolo11n.pt") I then provided multiple images: image_paths = [ r"D:\Python\images\dog.jpg", r"D:\Python\images\MyPic.jpg" ] results = model(image_paths) YOLO automatically performed object detection on each image and identified objects such as people, animals, vehicles, and other objects that the pretrained model recognizes. The interesting part was combining all the annotated images into one output image . This makes it ...

I Built a Team of AI "Employees" to Process Insurance Claims — In One Afternoon, For Free

Image
  The Problem With "One Big AI" Picture a health insurance claim landing on someone's desk. Before it gets approved or rejected, a human needs to: Check that all the paperwork is filled in correctly Confirm the treatment is actually covered by the policy Make sure nothing about the claim looks suspicious Understand the medical context well enough to judge if it makes sense Finally, make the call: approve, reject, or send it for closer review That's five different jobs, each needing a different kind of expertise. Now imagine trying to train one person to be equally good at all five. They'd be okay at everything and great at nothing. This is exactly the problem with asking a single AI prompt to "handle insurance claims." You get a jack-of-all-trades that misses details a specialist would catch. The fix? Don't hire one generalist. Hire a team. Meet the Team Here's what I actually built — a little assembly line of AI "employees,...

Simple experiment on Connect-MCP from Pega Infinity V25.1.3

Image
I recently conducted a simple hands-on exploration of the Connect-MCP rule type in Pega Platform 25.1.3 Community Edition. One of the interesting aspects of this experiment is that no custom code was required—the entire proof of concept was achieved through configuration alone. Depending on future use cases and integration requirements, custom code may become relevant, but this initial research demonstrates the power of a low-code approach. If you're interested in exploring MCP integrations within Pega, you can follow the simple four-step approach outlined in my post and try it out yourself. Very simple steps to build this functionality in your Commu nity Edition for initial learning perspective. This experiment is for education purpose only and this can be extendable later.  For now, I just had this simple usecase for my understanding on this OOTB feature. Step1: Create a simple Connect-MCP and configure with free MCP server. Here is another free server for the folks who want to ...

Connecting Claude to Pega Infinity 25.1.3 via MCP — Step-by-Step

Image
Enable AI-powered access to your Pega Investigative Case Management data directly from Claude prompts using the Model Context Protocol (MCP) and OAuth 2.0. What is MCP and why connect Pega to Claude? The Model Context Protocol (MCP) is an open standard that lets AI assistants like Claude securely call tools and read data from external systems — all from a natural-language prompt. Think of it as a universal adapter between your enterprise systems and AI. Pega Infinity V25.1.3 ships with a first-class MCP service built on its existing REST framework. Once enabled, Claude can: Query and summarize investigative cases without switching apps Retrieve assignment details and case status on demand Trigger Pega workflows from conversational prompts Version requirement: This guide is based on Pega Infinity V25.1.3 (Community Edition) with the Rule-Service-MCP rule type. Earlier versions may not include native MCP support. Architecture overview The connection uses three layers: Claude as the AI c...