ReplayAutonomous app testing for teams who ship at AI-speed
Promoted
Launching today
Cortex
Turn API specs into docs, SDKs, and MCP servers
396 followers
Turn API specs into docs, SDKs, and MCP servers
396 followers
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
@nick_csu Love the idea of keeping one source of truth for both developers and AI agents. Really smart approach 👏
Cortex
@ir3ne thank you!
how does this compare to tools like fern or stainless when it comes to SDK generation quality?
Cortex
@santosh__kumar9 Great question! Cortex provides full type safety for all generated SDKs, including GraphQL. It supports 11 languages, such as C++ and C, and allows custom generator configurations for specific edge cases. Plus, it's open-source (MIT License), ensuring no vendor lock-in! :)
Buffup.AI
does cortex generate types for all 11 languages automatically or do we need custom templates for languages like rust and go?
Cortex
@sansa_grey Great question! It generates SDKs automatically for all 11 languages. You'd only need to use custom generators if you have specific requirements, such as adding a custom license into the SDK.
I would love to know how it performs with large and messy real world specifications.
Cortex
@haolin That's a great point. We've already tested it with popular existing schemas, such as GitHub's GraphQL, to see how it generates SDKs, docs, and MCPs, and it worked flawlessly.
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 🚀🎊
Cortex
@aymi_malik Thanks for the question! I added validation support on the CLI to ensure the SDKs and MCP stay perfectly in sync with any spec changes.
love that its open source and MIT licensed. lock in with api tools is usually my biggest concern so this is refreshing.
Cortex
@favour_yusuf34 thanks! ensuring everything stays interoperable and open source is definitely a priority for the project
@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!
Cortex
@therayess Thanks! I'm glad you think the MCP approach is useful. Let me know how you find it when you try it out!