Inter-generational Tool Knowledge for your Agents

https://indiestack.fly.dev/

by Oatcake21 • 5 months ago

4 6 5 months ago

indiestack.fly.dev

Oatcake213• 5 months ago

A friend and I built indiestack because why build something that already exists? Need auth? It scaffolds from scratch instead of suggesting some free indie auth code out there. pip install indiestack) that plugs into Claude Code, Cursor, and Windsurf. When you ask your AI to build something, it checks our growing catalog of 480+ indie tools first. Every failed search gets logged as a market gap — so makers can see what developers actually need but can't find yet. Big or Small builds - anything you've got that solves any sort of problem, Indiestack is the place for it.

indiestack2• 5 months ago

https://indiestack.fly.dev/

indiestack2• 5 months ago

Co-founder here. One thing oatcake didn't mention -- the MCP server actually learns what you build with over time. It tracks category interests and inferred tech stack from your searches (never raw queries) and starts surfacing tools you wouldn't have found otherwise. You can see exactly what it stores and clear it anytime at /developer.

The market gap data has been the most interesting part. Every failed search gets logged and we're seeing real demand patterns for stuff that either doesn't exist or just isn't discoverable. Turns out there's a massive gap in developer file conversion tools -- that's not something we would have guessed.

I've personally contacted about 200 makers over the past few weeks and the pattern is always the same. Someone built something genuinely useful, it has maybe 50 GitHub stars, and nobody outside their immediate circle knows about it. The tools aren't bad, they're just invisible. There's no knowledge layer connecting what's been built to who needs it, especially not for agents.

The whole thing runs on Python/FastAPI/SQLite on a single Fly.io machine for about $5/mo. No React, no build step, pure Python string templates. 11 MCP tools including personalized recommendations and a stack builder that suggests full toolchains for a project description.

Oatcake213• 5 months ago

Yep - no brainier really. Be the second mouse.

mueslix• 5 months ago

Great. You added my project to your site without asking, then cold-emailed me about it, and wrapped the whole thing in a thin layer of "congratulations". Let me be direct: this is not flattering. It's spam.

On top of that, you're asking me to pay to "boost" something I never requested, and to help amplify your marketing on Hacker News. Essentially the holy trinity of:

1. Unsolicited outreach 2. Monetizing someone else's work without consent 3. Trying to recruit the very people you spam as your distribution channel

That's not community building. That's growth hacking at the expense of maintainers.

Oatcake213• 5 months ago

Fair criticism. We should have asked before listing and we're fixing that process. Your project has been removed. The cold email approach was wrong and we're learning from it — we're two students figuring this out, not a growth hacking operation. Appreciate the direct feedback.

Inter-generational Tool Knowledge for your Agents

Related Stories