<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: MCPForge</title><link>https://news.ycombinator.com/user?id=MCPForge</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 22 Oct 2026 10:58:53 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=MCPForge" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by MCPForge in "Ask HN: What are you working on? (June 2026)"]]></title><description><![CDATA[
<p>I'm building MCPForge.<p>The original idea came from repeatedly seeing the same workflow whenever someone wanted to expose an existing API to Claude, Cursor, or another agent:<p>* Parse an OpenAPI spec
* Generate tools
* Handle auth
* Deploy an MCP server
* Maintain it forever<p>I initially thought tool generation was the hard part.<p>After talking with developers, it seems the bigger challenges are authentication, permissions, endpoint selection, and safely exposing production APIs to AI agents.<p>MCPForge takes an OpenAPI spec or Postman collection and creates a hosted MCP endpoint. Recently, I've been spending more time on auth injection, tool permissions, and preventing destructive endpoints from being exposed by default than on generation itself.<p>Still very early (launched this week), and I'm mostly looking for feedback from people using MCP in production.<p><a href="https://www.mcpforge.tech" rel="nofollow">https://www.mcpforge.tech</a></p>
]]></description><pubDate>Mon, 15 Jun 2026 08:50:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=48538442</link><dc:creator>MCPForge</dc:creator><comments>https://news.ycombinator.com/item?id=48538442</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48538442</guid></item><item><title><![CDATA[New comment by MCPForge in "Show HN: I am running 3 coding agents non-stop over the last 3 days. Here is how"]]></title><description><![CDATA[
<p>What's interesting is that the hardest problem doesn't seem to be coding anymore. It's orchestration, approvals, and knowing when an agent should hand control back to a human.</p>
]]></description><pubDate>Sun, 14 Jun 2026 10:01:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=48525765</link><dc:creator>MCPForge</dc:creator><comments>https://news.ycombinator.com/item?id=48525765</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48525765</guid></item><item><title><![CDATA[New comment by MCPForge in "QodFlow – a Kanban board AI agents can drive via MCP"]]></title><description><![CDATA[
<p>request_human_decision feels like the key idea here. Most discussions focus on agent autonomy, but production systems usually need structured approval points.</p>
]]></description><pubDate>Sun, 14 Jun 2026 09:54:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=48525736</link><dc:creator>MCPForge</dc:creator><comments>https://news.ycombinator.com/item?id=48525736</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48525736</guid></item><item><title><![CDATA[New comment by MCPForge in "Show HN: Cortex – local-first encrypted memory for AI agents (Rust, MCP)"]]></title><description><![CDATA[
<p>Local-first memory makes a lot of sense. Curious whether you're treating memory as agent-specific or shared across multiple MCP-connected agents.</p>
]]></description><pubDate>Sun, 14 Jun 2026 09:52:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=48525727</link><dc:creator>MCPForge</dc:creator><comments>https://news.ycombinator.com/item?id=48525727</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48525727</guid></item></channel></rss>