I Built Postman for MCP Servers Because Debugging JSON-RPC Shouldn't Be Hell

<p>REST APIs gave humans (and the code they wrote) a standardized way to access software over the network.</p> <p>MCP is trying to do the same thing for agents.</p> <p>That simple

<h2> The Problem </h2> <p>The MCP ecosystem is expanding at an extraordinary pace. Anthropic, Microsoft, Google, AWS, and Cloudflare are all publishing official MCP servers.

<!-- SC_OFF --><div class="md"><p>The basic idea is simple: if you have an OpenAPI REST API, it makes it useable by AI agents with a single command without writing a MCP server

<p>Most MCP tutorials stop at a single stdio tool. These notes cover what I had to change once a server of mine had actual users, in the order the problems appeared.</p> <h2>

<h1> I Built a Pay-Per-Use MCP Server with 52+ Services </h1> <p>Every MCP server I found was either free (good luck scaling), subscription-based (hello, vendor lock-in), or

<p>The AI world has a plumbing problem. We have incredible language models, but connecting them to real tools — databases, APIs, file systems, other agents — still feels like

<p><a class="article-body-image-wrapper"

<!-- SC_OFF --><div class="md"><p>Built a Rust CLI that auto-discovers subcommands and flags from any command-line tool's <code>--help</code> and exposes them as MCP tools. Your