<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Deployment on Godberry Studios | Web Scraping &amp; Automation Tools</title>
    <link>https://godberrystudios.com/tags/deployment/</link>
    <description>Recent content in Deployment on Godberry Studios | Web Scraping &amp; Automation Tools</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 14 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://godberrystudios.com/tags/deployment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building Production-Ready MCP Servers: The 2026 Deployment Playbook</title>
      <link>https://godberrystudios.com/posts/deploy-mcp-server-production/</link>
      <pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://godberrystudios.com/posts/deploy-mcp-server-production/</guid>
      <description>&lt;p&gt;You built an MCP server. It works on your laptop. Claude connects, tools fire, results come back. Ship it, right?&lt;/p&gt;&#xA;&lt;p&gt;Not so fast. An April 2026 scan of 2,181 remote MCP server endpoints found that &lt;strong&gt;52% were completely dead&lt;/strong&gt;. Only 9% were fully healthy. The rest? Degraded — responding slowly, returning stale data, or failing silently with 200 OK responses full of parsing errors.&lt;/p&gt;&#xA;&lt;p&gt;The gap between &amp;ldquo;works locally&amp;rdquo; and &amp;ldquo;works in production&amp;rdquo; is where MCP servers go to die. This guide covers the architecture, tooling, and operational patterns that keep yours in that 9%.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
