Live data from Hacker News

Launch HN: Manufact (YC S25) – MCP Cloud

manufact.com

11–20 of 81 posts

Re: Launch HN: Manufact (YC S25) – MCP Cloud

#11
post #2

MCP is a deadend. CLI use is the future.

MCP is great for docs and stuff, also saves tokens and reduces errors if you have something complicated you're abstracting over

- agents have old/inaccurate knowledge and it's nice to have up to date docs: https://awslabs.github.io/mcp/servers/aws-documentation-mcp-...

- geting agents to do apple builds and stuff is much easier with: https://github.com/getsentry/XcodeBuildMCP

- also for searching stuff like pdfs/epubs it's nice to have a place that's easy/fast for an agent to go to: https://github.com/nburns/doc-search-mcp

none of these strictly requrie mcp, but it is still a useful abstraction/shared convention

Re: Launch HN: Manufact (YC S25) – MCP Cloud

#12
post #2

MCP is a deadend. CLI use is the future.

I am so tired of people repeating this. Usually, this results from conflating two uses of MCP: local, which can indeed be replaced by CLI (and you can argue which one is better), and remote, which is entirely different, and there is no way to replace it with a CLI (note that you are making an implicit assumption that a CLI tool can be used at all, which is not always the case).

Please don't repeat this. It's like saying that apples are dead and oranges are the future.

Re: Launch HN: Manufact (YC S25) – MCP Cloud

#13
post #3
post #2

MCP is a deadend. CLI use is the future.

Could you elaborate on this thought? MCP vs CLI feels very much like a Apples/Oranges comparison, without additional context.

MCP makes a lot, lot more sense when you think of it as as a auth standard and not a comparison with CLIs. It obviously does more than just auth, but having standardised auth (which CLIs definitely do not) is the real 'killer' feature.

Re: Launch HN: Manufact (YC S25) – MCP Cloud

#14
post #10

Earlier quoted context omitted.

They serve two different purposes. Edited*

> Tell me you don't understand what you're saying without telling me you don't understand what you're saying. Please don't cross into personal attack, regardless of how wrong someone is or you feel they are. Your comment would be fine without that last swipe, and even better if you had gone on to say what the two purposes are. Then we could learn something from it. If you wouldn't mind reviewing https://news.ycombina…

Apologies, I appreciate you posting this!

Re: Launch HN: Manufact (YC S25) – MCP Cloud

#16
This is cool. I was skeptical of MCP's until I made one recently. They're essentially the exact same as 1) giving your agent a CLI tool or REST API and 2) pointing it there in an AGENT.md/CLAUDE.md. Agents are great at using built-for-human CLI tools and IMO they don't need anything purpose-built for agents. The key difference, which ends up being a usability win for non-technical users, is that the MCP bundles 1 and 2 - harnesses inject the MCP tool descriptions on every session after install. Of course, that's also why you need to be careful about context bloat when using/building them

Re: Launch HN: Manufact (YC S25) – MCP Cloud

#19

MCP is something people think of as a "panacea" to all AI issues. I think people are beginning to realize it is just one, albeit important, part of a successful AI architecture.

First of all, people have been saying this for a long time. It’s nothing new, at least half a year, maybe closer to a year.

Secondly, it’s not even that important, it’s the tool calling itself that’s important. MCP servers are just a convenient way to interact with remote services when a command line utility for the same would be inconvenient.

Post reply on HN