<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agents on Simple Enough Blog</title><link>https://blog.dev.simpleenough.net/tags/agents/</link><description>Recent content in Agents on Simple Enough Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 03 Jun 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://blog.dev.simpleenough.net/tags/agents/index.xml" rel="self" type="application/rss+xml"/><item><title>MCP Servers: Understanding the Model Context Protocol</title><link>https://blog.dev.simpleenough.net/blog/mcp/</link><pubDate>Wed, 03 Jun 2026 10:00:00 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/mcp/</guid><description>&lt;p>Language models are brilliant at reasoning over text, but by nature they are cut off from the world. A model cannot read your files, query your database, or call an API unless it is explicitly given the means to do so. The &lt;strong>Model Context Protocol (MCP)&lt;/strong> is the standard that solves this problem in a generic way. This first article lays the groundwork; the next ones will dive into building a server and integrating it into an ecosystem.&lt;/p></description></item></channel></rss>