<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Rest on AuthenticBits</title><link>https://authenticbits.net/tags/rest/</link><description>Practical tools, real-world lessons, and honest reflections on engineering leadership</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 14 Jan 2026 21:28:32 +0100</lastBuildDate><atom:link href="https://authenticbits.net/tags/rest/index.xml" rel="self" type="application/rss+xml"/><item><title>MCP for the REST of Us</title><link>https://authenticbits.net/blog/mcp-for-the-rest-of-us/</link><pubDate>Wed, 14 Jan 2026 21:28:32 +0100</pubDate><guid>https://authenticbits.net/blog/mcp-for-the-rest-of-us/</guid><description>If you've been anywhere near AI tooling lately, you've probably heard about MCPs. Let me break down what MCP actually is, why it exists, and how it differs from the RESTful paradigm we've all grown comfortable with.</description><media:content url="https://authenticbits.net/blog/mcp-for-the-rest-of-us/mcp.webp" medium="image"/></item></channel></rss>