Cortex is an open source API knowledge layer that turns OpenAPI, AsyncAPI, GraphQL, gRPC, and OpenRPC specs into interactive documentation, typed SDKs in 11 languages, and MCP servers for AI agents.
Hey Product Hunt 👋
I’m Nick, and I built Cortex because being an engineer in the AI era means your APIs increasingly need to serve two very different users: developers and AI agents.
But supporting both often means doing the same work twice. You build documentation and SDKs for developers, then create separate MCP tools and context for agents.
Today, these pieces are usually maintained separately. They drift out of sync, create duplicate work, and leave AI agents trying to understand your API from incomplete or outdated context.
Cortex makes your API contract the source of truth.
Give it your OpenAPI, AsyncAPI, GraphQL, gRPC, or OpenRPC specs, plus Markdown, and Cortex generates:
📚 Interactive documentation for developers
⌨️ Typed SDKs across 11 languages
🤖 MCP servers with typed tools and grounded API context
Everything is open source and MIT licensed. You can customize the templates, publish the SDKs wherever you want, and host the generated documentation yourself.
The idea is simple: define your API once, then give every developer and every agent the interface they need to actually use it.
Check out the open source repo at https://github.com/cortex-docs/c...
I would love feedback from teams building APIs, SDKs, developer tools, and agent integrations.
What would make Cortex more useful in your workflow?
we run a small mcp server, 28 tools, and the part that took longest was not the types. it was the descriptions.
two of ours read "fetch before prospecting to skip duplicates" and "stored as DRAFT, not sent". neither of those is in any schema. the first is an ordering rule, the second is there so the agent doesnt tell you it sent something that is only queued.
a spec gives you the shape of every call and nothing about which of two similar endpoints is the right one. for the sdk thats fine, the developer reads the page. for the agent that one string is the whole basis of the decision.
so when you generate the mcp server, what goes into the tool description? the summary field from the spec, or something else?
The SDK generation is that your own work or are you using the one from OpenAPI ? The C# generation from openapi is a a messy code bloat.
sometimes I start with the docs but then get distracted rewriting API calls. if Cortex auto-generates integration code from specs, might save me from wandering off before everything's written up. but I always skip reading the full spec first, so who knows.
Love that Cortex treats AI agents and developers as first class consumers of the same spec, generating one source of truth into SDKs, docs, and MCP servers instead of duplicating the work.
I would be interested to see how it custom code when teams need behavior beyond what the API spec defines.
Regarding the auto-generation of SDKs for 11 programming languages, what is your approach to ensuring consistency with any changes to the original specification, auto-regeneration on every change or manual intervention? BTW, Congratulations @nick_csu & @fmerian on the launch of Cortex 🚀🎊
Looks another amazing product. Congrats @nick_csu & team!
Thanks for sharing @fmerian 🙌🏻
I would love to know how it performs with large and messy real world specifications.
11 languages? my team can barely maintain two definitely giving this a shot over the weekend!
The docs preview looks super clean. genuinely impressive work on unifying asyncapi and openapi into one workflow.
@nick_csu the idea of interactive API docs sounds sweet, for me, the way i'd use this is via mcp, being a SWE myself, and i find this solution useful personally, gonna try it out, thanks!
11 languages? my team can barely maintain two... definitely giving this a shot over the weekend!
we have a mix of graphql and REST endpoints in one project. can cortex bundle both into a single mcp server or do we split them?
love that its open source and MIT licensed. lock in with api tools is usually my biggest concern so this is refreshing.
does cortex generate types for all 11 languages automatically or do we need custom templates for languages like rust and go?
how does this compare to tools like fern or stainless when it comes to SDK generation quality?
About Cortex on Product Hunt
“Turn API specs into docs, SDKs, and MCP servers”
Cortex launched on Product Hunt on September 12th, 2026 and earned 243 upvotes and 32 comments, earning #2 Product of the Day. Cortex is an open source API knowledge layer that turns OpenAPI, AsyncAPI, GraphQL, gRPC, and OpenRPC specs into interactive documentation, typed SDKs in 11 languages, and MCP servers for AI agents.
Cortex was featured in API (98.6k followers), Open Source (68.8k followers), Developer Tools (519.2k followers) and GitHub (41.4k followers) on Product Hunt. Together, these topics include over 139k products, making this a competitive space to launch in.
Who hunted Cortex?
Cortex was hunted by fmerian. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Cortex stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
fmerian