Incultnito Studio
Brief-first apparel workflow with a public fulfillment MCP
4 followers
Brief-first apparel workflow with a public fulfillment MCP
4 followers
Write one brief. We generate print-ready art, composite it on garments, and route the order through Printful or your factory webhook today. 4 more adapters in queue. Public MCP, 275 tests. Solo non-coder, all Claude-paired.
Interactive
Free Options
Launch Team / Built With
Hey Product Hunt 👋 Peng here — solo founder out of Taipei. Incultnito Studio is the apparel design workflow I built for myself because freelance designers were charging me $800 a concept round and I was waiting 10 days to get a mockup back wrong. I'm not a traditional engineer — every line of production code in Studio was written with Claude as my engineering partner. I just directed it.
What it does today:
- 📝 Brief-first workflow: one sentence → three concept directions in 60s
- 🧵 Printful catalog (4 flagship SKUs, live Stripe checkout, real draft orders)
- 🔌 Public Fulfillment MCP at `incultnito.com/mcp` — 2 production-validated adapters (Printful, HMAC webhook) + 4 code-complete adapters in vendor onboarding (Apliiq, ooShirts, Scalable Press, MCP Proxy). One contract, six destinations — adding the next is a config change, not a rewrite.
- 🤖 Agent Hub — Brief Interpreter live, 5 more agents on waitlist
- 🔑 Workspace-scoped self-serve MCP tokens (SHA-256, copy-once, revocable)
- 📦 Adapter SDK published MIT: `@incultnito/adapter-sdk`
- 🧪 275 test cases, CI green, pre-commit security hook on OWASP Top 10
- 🎬 Interactive demo (zero signup): [incultnito.com/demo](https://incultnito.com/demo) — click through the full workflow in 60 seconds
What's coming next (Q3):
- Out the Lab — upload your own garment photo, SAM-segment it, composite generated art on the real surface (not our catalog)
- Adapter Marketplace — community-contributed fulfillment destinations
- Brief API (white-label for enterprise) I'm here all day — ask me anything, especially about building a SaaS solo as a non-coder.
The full commit history is public, so no smoke, no mirrors.
→ Free to try: https://incultnito.com
→ MCP manifest (for AI-native folks): https://incultnito-v2.onrender.com/mcp/manifest
→ GitHub (case study lives in the transcripts): https://github.com/incultnitollc/incultnito_v2
Thank you for even looking. 🙏
@incultnito Hour 18 update — EU morning is showing up. 🇪🇺
Quick context for new folks landing here:
Incultnito Studio is operator workflow on top of a public Fulfillment MCP router. The router holds 6 adapter slots — two production-validated (Printful, HMAC webhook), three code-complete with active vendor onboarding (Apliiq, Gooten, T-Pop), and one (Scalable Press) code-complete and waiting for that vendor's partner program to reopen.
The point is not the adapter count. The point is that the contract is the product. One MCP router, any printer adapter swaps in beneath it. Operators don't rewrite their workflow when fulfillment changes — they reroute.
If you run a print-on-demand vendor and want your service in the router, the SDK is on npm (@incultnito/adapter-sdk, MIT). Write an adapter, PR it back, ship to every operator on the platform.
If you're an operator looking at this and your current fulfillment stack feels brittle — that's exactly the surface area this router fixes.
DM open. Onboarding queue is forming.