<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Developer-Tools on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/developer-tools/</link>
    <description>Recent content in Developer-Tools on BLAZED.sh Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 10 Aug 2026 16:00:00 +0000</lastBuildDate>
    <atom:link href="https://blazed.sh/blog/tags/developer-tools/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>An MCP Server in One Bash File</title>
      <link>https://blazed.sh/blog/posts/mcp-server-in-one-bash-file/</link>
      <pubDate>Mon, 10 Aug 2026 16:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/mcp-server-in-one-bash-file/</guid>
      <description>&lt;p&gt;BLAZED.sh is a PaaS for latency-sensitive workloads. Users can deploy OCI containers or run JavaScript scripts without managing the servers below them.&lt;/p&gt;&#xA;&lt;p&gt;The platform already had a REST API, and while building our CLI we also wanted an MCP server. An agent should be able to deploy something, stop it and read its logs using the same API as everyone else. Our first thought was to start another TypeScript project and install an MCP SDK. Then we realized that the Bash CLI already did nearly all of the work.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
