<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI on psLens</title><link>https://pslens.com/categories/ai/</link><description>Recent content in AI on psLens</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 14 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://pslens.com/categories/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Connecting AI Coding Agents to PeopleSoft with Model Context Protocol (MCP)</title><link>https://pslens.com/blog/connecting-ai-agents-to-peoplesoft-with-mcp/</link><pubDate>Fri, 14 Aug 2026 00:00:00 +0000</pubDate><guid>https://pslens.com/blog/connecting-ai-agents-to-peoplesoft-with-mcp/</guid><description>&lt;p&gt;PeopleSoft has always been a black box to modern AI coding assistants.&lt;/p&gt;
&lt;p&gt;Tools like &lt;a href="https://claude.ai/code"&gt;Claude Code&lt;/a&gt;, &lt;a href="https://www.cursor.com"&gt;Cursor&lt;/a&gt;, and &lt;a href="https://claude.ai/download"&gt;Claude Desktop&lt;/a&gt; work by reading files on disk, navigating Git repositories, and parsing project trees. PeopleSoft does not work like that. Its object definitions, record structures, SQL objects, and PeopleCode live inside relational database tables (&lt;code&gt;PSRECDEFN&lt;/code&gt;, &lt;code&gt;PSRECFIELD&lt;/code&gt;, &lt;code&gt;PSPROGMETA&lt;/code&gt;, &lt;code&gt;PSAEAPPLDEFN&lt;/code&gt;), not on the filesystem.&lt;/p&gt;
&lt;p&gt;Until now, getting that context to an LLM required writing ad-hoc SQL queries, taking screenshots of Application Designer, or manually copying and pasting code blocks into a chat window. That workflow is slow, breaks context across object hierarchies, and makes autonomous coding assistants impossible to use with PeopleSoft.&lt;/p&gt;</description></item></channel></rss>