Product Thumbnail

Doccupine

Open source AI-ready documentation platform.

Open Source
Developer Tools
Artificial Intelligence

Hunted byLuan GjokajLuan Gjokaj

Open source CLI turns your Markdown or MDX files into beautiful documentation. Bring your own AI model plus MCP support. Our hosted platform includes a visual editor, pending changes, custom domains, and team collaboration.

Top comment

Hi Product Hunt! I'm Luan, one of the founders here at Doccupine.

I've always struggled to find solid documentation tooling. Most solutions are too expensive or too complex. If that's not the case, they're locking you in with proprietary tech. None of them let you bring your own AI model or integrate your docs directly into AI development workflows.

Doccupine is an open source CLI (npx doccupine). It turns Markdown and MDX files into a complete documentation website. You can self host it on your server for free. You can also bring your own AI model. To start, we have 12+ popular models from OpenAI, Anthropic, and Google (and we will be adding more). Plug in your API keys and go. Doccupine also comes with an MCP server out of the box.

We're monetizing through our managed platform. It's for teams who want user roles and permissions, easy front-end editing, managed AI with transparent budget caps (you can also still bring your own AI model), zero-config deploys, and automatic updates. We're bootstrapped. Two founders, no VC. We answer every support email. 

We'd love your feedback. What would make Doccupine useful for you?

Comment highlights

Solid for devs turning Markdown/MDX into AI-ready docs with collaboration is handy. Could land stronger with the key outcome up front build beautiful AI powered docs from your files, with team collaboration and custom domains.

How does it compare to @Documentation.AI?

Congratulations on the launch! One of the benefits of markdown is that it is stylistically simple but information rich, and your description isn't (yet) selling me the idea that turning it into a website is useful. Some more explanation, or some before-and-after examples, e.g. a repo containing the md files and a link to the compiled website, would help pitch it to me.

Congrats on the launch! 🎉

The MCP support is what really caught my attention — most documentation tools treat AI as an afterthought, but baking it in from the CLI level is a smart architectural decision.

Quick question: how does Doccupine handle versioning for docs? For example, if I'm documenting a web tool that ships updates frequently, can I maintain v1 and v2 docs side by side without duplicating everything?

The Markdown → beautiful docs pipeline looks really clean.

Upvoted and following to see where this goes! 🚀

Great launch, @luangjokaj. Open source doc tool with MCP support. That's something I don't see every single day.


I spent about 10 minutes going through the site. One thing caught my attention. You're leading hard with AI features. 12 models. Bring your own. MCP server. All good things. But here's the thing. Devs are tired of AI being the main character in every product. The part that got me excited was "npx doccupine" and done. That's the dream. No setup. No config.

Also looked at your pricing. $200/month for Pro with one project. Compared to self-hosting for free, I'm not sure what I'm paying for. AI-Powered Documentation Assistant sounds nice but what does it actually do? If it's just plugging in my API key, that's a tough sell.

Curious how you're thinking about this. Either way, cool to see someone building in the open.

this is actually pretty nice tbh. docs are one of those things teams need badly, but the tooling around them often ends up being weirdly costly or too opinionated. i like that this gives people a simpler path and still lets them use their own ai setup.

curious, what kind of teams are getting into it fastest right now, solo devs shipping docs or proper teams replacing older tools?

This is a strong direction. A lot of documentation tools either get expensive fast or box teams into their own way of working, so the open-source plus bring-your-own-model angle makes this stand out. The MCP support also makes it feel more aligned with where developer workflows are heading.

Curious, are most people starting with the self-hosted CLI route first, or going straight to the managed platform?