<?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 Simple Enough Blog</title><link>https://blog.dev.simpleenough.net/tags/mcp/</link><description>Recent content in MCP on Simple Enough Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 17 Jun 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://blog.dev.simpleenough.net/tags/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>MCP Servers: Integration and Ecosystem</title><link>https://blog.dev.simpleenough.net/blog/mcpecosystem/</link><pubDate>Wed, 17 Jun 2026 10:00:00 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/mcpecosystem/</guid><description>&lt;p>In the first article, we laid the groundwork for the Model Context Protocol; in the second, we built a server from end to end. That leaves the question that turns a prototype into an everyday tool: &lt;strong>how do you integrate an MCP server into your working environment, reusing the existing ecosystem, without opening a security hole?&lt;/strong> That&amp;rsquo;s the subject of this final article.&lt;/p>
&lt;hr>




&lt;h2 id="i-connecting-a-server-to-claude-and-claude-code" class="heading">I. Connecting a server to Claude and Claude Code&lt;a href="#i-connecting-a-server-to-claude-and-claude-code" aria-labelledby="i-connecting-a-server-to-claude-and-claude-code">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>In the tutorial, we connected our server to Claude Desktop through &lt;code>claude_desktop_config.json&lt;/code>. &lt;strong>Claude Code&lt;/strong>, the command-line assistant, offers an even more direct approach with the &lt;code>claude mcp&lt;/code> subcommand:&lt;/p></description></item><item><title>Tutorial: Building Your First MCP Server in Python</title><link>https://blog.dev.simpleenough.net/blog/mcptuto/</link><pubDate>Wed, 10 Jun 2026 10:00:00 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/mcptuto/</guid><description>&lt;p>In the first article on Model Context Protocol servers, we laid the groundwork: its host / client / server architecture and its three primitives (tools, resources, prompts). Now for the practical part. In this tutorial, we build a small MCP server in Python from end to end, exposing one &lt;strong>tool&lt;/strong> and one &lt;strong>resource&lt;/strong>, then we connect it to a host to watch a model use it.&lt;/p>
&lt;hr>




&lt;h2 id="i-prerequisites-and-installation" class="heading">I. Prerequisites and installation&lt;a href="#i-prerequisites-and-installation" aria-labelledby="i-prerequisites-and-installation">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>You need &lt;strong>Python 3.10 or higher&lt;/strong>. The official SDK also ships a handy command-line utility to test and install a server.&lt;/p></description></item><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>