# Pega Blueprint — AI Connector Pega Blueprint publishes 1 MCP tool to Claude. Marketplace availability, tool surface, verification tier, and what Node8 measured against the live endpoint. Source: https://node8.ai/ai-connectors/developer-tools/pega-blueprint/ --- [AI Connectors](https://node8.ai/ai-connectors/) · [Developer Tools](https://node8.ai/ai-connectors/developer-tools/) # Pega Blueprint Turn a plain-language brief into a Pega application design Listed in Claude · 1 published tool · Community-listed [Claude connector docs](https://www.pega.com/blueprint) [pega.com](https://www.pega.com/) Overview ## What Pega Blueprint does Pega Blueprint generates application designs for the Pega Platform from a written description rather than from a modelling session. The connector exposes that generation engine through a single tool call: a described requirement comes back as a design with case lifecycle stages, the steps inside each stage, plus the data objects, channels, and personas that support them. Because the whole design is produced in one call, refinement happens by regenerating from a changed brief, so the conversation itself becomes the iteration loop. Designs follow the platform's established patterns, and the result carries into the Pega Platform for build. One tool is published, and the endpoint requires an account before responding. ### Who it is for Business analysts and solution architects scoping applications for the Pega Platform. ### Tool surface A single published tool is unusual in this catalogue, and the endpoint's credential requirement means even that one name went unobserved, though the design as described completes in one round trip. Availability ## Where Pega Blueprint is listed Pega Blueprint is listed in the Claude connectors directory only. Pegasystems has no app under the same domain in the ChatGPT directory; 392 of the 3,150 products here are on both marketplaces, and this is not one of them. The MCP server behind a Claude connector is usually the same server a ChatGPT app would need, so the absence is a distribution decision rather than a technical one. Claude listing ## In the Claude connectors directory Pega Blueprint publishes 1 tool to Claude, a deliberately narrow surface; only 0.7% of the 1,253 Claude-listed connectors expose fewer. The median Claude-listed connector filed under Developer Tools publishes 13, so this one sits 12 tools below its bucket's median, 91st of 95. It falls in the 1-3 tools band, which holds 16.4% of the Claude directory. Pega Blueprint publishes a remote MCP endpoint. Claude connects to it over HTTP; there is nothing to install locally. Every connector in the Claude directory is remote, all 1,253 of them, so transport is not a differentiator there. Publisher Pegasystems Verification Community-listed (61.5% of the Claude directory) Filed under Developer Tools Endpoint `https://mcp.pega.com/prweb/app/dcoai/api/service/v1/mcp/default` Documentation [Publisher setup docs](https://www.pega.com/blueprint) Published tools 1 · 1-3 tools band Depth rank in Developer Tools 91 of 95 Snapshot August 2026 Pega Blueprint is community-listed in the Claude directory, the tier 770 of 1,253 connectors sit in (61.5%). It is the default for a self-published server, and says nothing either way about quality. In the publisher's words ## How Pegasystems describes it > Pega Blueprint is an AI-powered application design tool that accelerates delivery from early discovery to production go-live, keeping governance and best practices front and center. This connector exposes Blueprint's generation engine to Claude via MCP, letting users turn a plain-language idea into a complete, build-ready application design without leaving the conversation. A user describes what they want, and Claude calls the Blueprint tool to produce a full design in one step: case lifecycle stages, the steps within each stage, supporting data objects, channels, and personas. The result can be reviewed conversationally and carried into the Pega Platform for build. Because generation happens through a single tool call, Claude can iterate in dialogue — refining stages, expanding data models, or reframing the workflow — and regenerate as the conversation evolves. Designs follow established architectural patterns rather than ad-hoc structure, with security and governance built into the foundation and data kept under the customer's control. Teams use Blueprint to move from initial concept to a working application far faster than traditional design approaches allow. Quoted from the connector's own Claude directory listing as captured in August 2026. Node8 did not write it and does not vouch for it. Nearby ## Other Developer Tools connectors ### [GraphOS MCP Tools](https://node8.ai/ai-connectors/developer-tools/graphos-mcp-tools/) Apollo docs, connector specs, and GraphOS graph telemetry Claude ### [OpenAI Developers](https://node8.ai/ai-connectors/developer-tools/openai-developers/) Building AI apps and agents with OpenAI tooling ChatGPT ### [swatchdog](https://node8.ai/ai-connectors/developer-tools/swatchdog/) Checks generated UI code against a design token set Claude ### [Apiiro Guardian](https://node8.ai/ai-connectors/developer-tools/apiiro-guardian/) Application security risk context from an Apiiro deployment Claude ### [Build Web Data Visualization](https://node8.ai/ai-connectors/developer-tools/build-web-data-visualization/) Design and build browser-based charts and dashboards ChatGPT ### [CircleCI](https://node8.ai/ai-connectors/developer-tools/circleci/) CI configuration and build troubleshooting inside Codex ChatGPT [All 188 Developer Tools connectors](https://node8.ai/ai-connectors/developer-tools/) This is an independent catalogue entry compiled by Node8 from Pega Blueprint's public marketplace listing as it stood in August 2026. Listing facts come from the marketplaces; the comparisons against the rest of the directory and any live-endpoint measurements are Node8's. Node8 is not affiliated with Pegasystems, and inclusion here is not an endorsement. ## Want your company reachable inside ChatGPT and Claude? Node8 builds MCP servers end to end: deciding which tools are worth exposing, the authentication and permission model, the review submissions, and the onboarding that gets them used. One server serves ChatGPT, Claude, and Microsoft Copilot. [See how it works](https://node8.ai/mcp) Book a strategy session