stugreen13

Yep - as long as it's public url can crawl it. Lmk if any issues will fix

Depends on use-case for sure - I think there is room for both

MCP

> learn new protocol

> bloat your context with unnecessary tools

> decision overload for agents

> spin up new server, more code to document and maintain

> pain to debug

> constantly changing

CLIs

> 0 context bloat

> one-line install

> on-demand discovery via --help commands

> fast and lightweight

> every model knows bash, even dumb ones

> composable, can chain commands (massively underrated, e.g. cli users list --output json | jq '.[].id' )

> save $$$ on tokens

> no new servers or docs

> can use tools like https://instantcli.com to generate one for any API

MCP is a mess, CLIs are the way

Yep can use spec or docs

Great stuff. Would be neat to have an adapter make the output stream match the ai-sdk format so it plugs in to existing UX (https://sdk.vercel.ai/docs/ai-sdk-ui/stream-protocol)

Great point thank you - will add a section on this to the landing page

Indiehost is even more of an abstraction (sign in with cloud provider and we do the rest) vs. Coolify Cloud still requires configuring your servers + resources + understanding of Coolify (e.g. proxies, redirects, ssh keys, backups, etc.)

Of course, the abstraction has its drawbacks (limited control) and I always recommend self-hosting. It's a template for the most common scenarios for new devs/app devs who may shy away from self-hosting for many reasons (takes too much time, not-reliable, fear of the unknown)

Ah thanks for pointing this out - was not familiar with that rule

Deleting and moving to regular submission

super cool. this would be next-level with openai's real-time voice API

nice - super clean and lightweight. what are you parsing raw request strings for?