[unglaublich]

I thought the concensus was slowly converging to using clear CLIs + skills (i.e. progressive disclosure) instead of MCPs to avoid the context pollution.

[julius]

CLIs need installs. What if your customer uses Web-based Agent? What if your customer has IT that does not easily allow install/updates of your CLI?

CLIs are working better with current harnesses in my experience, but no idea how I would ship them.

[0123456789ABCDE]

i've used pypi, which enables: `uvx <package name>` or `uv tool install <package name>` for a more permanent setup

some folks go to the trouble of publishing with `brew`

then there's the old `curl -LsSf https://example.com/install.sh | sh`

[lurking_swe]

what about web apps that requires oauth login - for normal users?

For example, is a typical Google Drive user expected to install an official google drive CLI and a skill md file just to interact with Google Drive in the chatgpt app? That seems absurd, IMO. Clicking “install” via an MCP / Plugin marketplace and then logging in via Oauth is less confusing.

MCP is also way more convenient (as a user) if i’m interacting with an API that supports oauth anyway. I don’t need to generate an api key, install a binary, create an md file, etc. CLIs and skills are great too! But not always the best choice.

[0123456789ABCDE]

parent is right, but so are you

note: cli tools do auth too — gh and claude code itself have some of the nicest auth flows i've experienced