<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: 56 Prince Pal</title>
    <description>The latest articles on DEV Community by 56 Prince Pal (@56_princepal_a4d5346a99d).</description>
    <link>https://dev.to/56_princepal_a4d5346a99d</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4009988%2F42aa6a25-832b-40b2-844a-3de5d2a57a3b.jpg</url>
      <title>DEV Community: 56 Prince Pal</title>
      <link>https://dev.to/56_princepal_a4d5346a99d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/56_princepal_a4d5346a99d"/>
    <language>en</language>
    <item>
      <title>mcpgen: Turn any OpenAPI spec into an MCP server in seconds</title>
      <dc:creator>56 Prince Pal</dc:creator>
      <pubDate>Tue, 30 Jun 2026 18:11:49 +0000</pubDate>
      <link>https://dev.to/56_princepal_a4d5346a99d/mcpgen-turn-any-openapi-spec-into-an-mcp-server-in-seconds-5cd7</link>
      <guid>https://dev.to/56_princepal_a4d5346a99d/mcpgen-turn-any-openapi-spec-into-an-mcp-server-in-seconds-5cd7</guid>
      <description>&lt;p&gt;I got tired of manually writing MCP tools for every REST endpoint I wanted&lt;br&gt;
to expose to an LLM. So I automated it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;mcpgen&lt;/strong&gt; reads an OpenAPI JSON or YAML file and generates a complete,&lt;br&gt;
ready‑to‑run MCP server in Python.&lt;/p&gt;




&lt;h2&gt;
  
  
  🔧 What it does
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Parses OpenAPI 3.0 / 3.1 specs&lt;/li&gt;
&lt;li&gt;Creates one MCP tool per endpoint (with &lt;code&gt;snake_case&lt;/code&gt; names)&lt;/li&gt;
&lt;li&gt;Handles auth automatically (API key, Bearer, etc.)&lt;/li&gt;
&lt;li&gt;Outputs a clean, human‑readable Python script&lt;/li&gt;
&lt;li&gt;Zero runtime surprises – just &lt;code&gt;mcp&lt;/code&gt; and &lt;code&gt;httpx&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  🚀 Quick start
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
bash
pip install mcpgen
mcpgen my-api.json -o my-mcp-server
python my-mcp-server/server.py
The generated server runs over stdio – ready to plug into Claude Desktop
or any MCP client.

🧪 Real‑world test
Recently a contributor added an OpenAPI 3.1 fixture (Xquik API) with
lookupTweet and getUser endpoints. The tool generated the correct
tools, including path parameters and x-api-key auth, on the first try.

All 18 tests pass. It works.

🤔 Why you might want it
If you’re building LLM agents that need to interact with APIs,
mcpgen eliminates the boilerplate. You don’t have to write a single
@app.tool() decorator by hand.

It also makes it dead simple to experiment – change your API spec,
regenerate the server, and you’re done.

📦 Links
GitHub: JnanaSrota/mcpgen

PyPI: pip install mcpgen

MIT licensed, open to contributions

🙏 Feedback
If you try it with your own API spec and something breaks (or works
beautifully), I’d love to hear about it. Drop a comment or open an issue.

Thanks for reading!
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
      <category>python</category>
      <category>api</category>
      <category>mcp</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
