<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HTTP on</title><link>https://eunus.dev/tags/http/</link><description>Recent content in HTTP on</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0600</lastBuildDate><atom:link href="https://eunus.dev/tags/http/index.xml" rel="self" type="application/rss+xml"/><item><title>Model Context Protocol Series 1 — Building a Production MCP Server in .NET with HTTP Transport</title><link>https://eunus.dev/blog/model-context-protocol-series-1-building-a-production-mcp-server-in-.net-with-http-transport/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0600</pubDate><guid>https://eunus.dev/blog/model-context-protocol-series-1-building-a-production-mcp-server-in-.net-with-http-transport/</guid><description>I was building a multi-tenant SaaS platform on ABP Framework and kept hitting the same wall: I wanted Claude to create tenants, query bookings, and manage configuration — not by generating code for me to run, but by calling the actual API directly. Like giving an AI assistant a real key to the backend, not a stack of printed instructions.
That&amp;rsquo;s exactly what MCP enables. But once I started digging, every tutorial I found showed stdio — a local process Claude spawns and kills.</description></item></channel></rss>