<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MCP on René Welches</title><link>https://blog.renewelches.com/tags/mcp/</link><description>Recent content in MCP on René Welches</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 22 May 2026 15:08:07 -0400</lastBuildDate><atom:link href="https://blog.renewelches.com/tags/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Beyond API Standardization: MCP and Agent Auth</title><link>https://blog.renewelches.com/2026/05/22/api-standardization-mcp-auth/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://blog.renewelches.com/2026/05/22/api-standardization-mcp-auth/</guid><description>&lt;p&gt;I recently went through three rounds of interviews for an API Technical Lead position. The company wanted someone to own their API standardization story end-to-end: define the standards, choose the tooling, drive (enforce) adoption across engineering teams. A classic platform engineering mandate.&lt;/p&gt;
&lt;p&gt;By the third interview it became clear that what they were actually trying to solve wasn&amp;rsquo;t API standardization in the traditional sense. They were trying to get their systems &lt;em&gt;AI-ready&lt;/em&gt;. And that realization opened up a more interesting conversation than the one we&amp;rsquo;d been having.&lt;/p&gt;</description></item></channel></rss>