Launch HN: Manufact (YC S25) – MCP Cloud

Join the discussion

• Hacker News
• On your website under "Thousands of dev-teams are building with mcp-use" you include a quote from your CTO (@enri). If thousands of teams are using the product, I would think you could omit this post.

  I think you have a really neat product here, but these types of testimonials do you more harm than good; they sour my opinion of all other testimonials on your site. I shouldn't have to play detective.

  by zxela
• noted! thanks for the feedback, will be gone soon edit: gone
  by pzullo
• we've been using manufact for months now. couldn't build mcps another way.
  by sebastiancrossa
• MCP is a deadend. CLI use is the future.
  by sampton
• They serve two different purposes.

  Edited*

  by Catloafdev
• cached thought. running CLIs is impractical and expensive in many environments and a hell of a lot less secure than using MCP
  by phpnode
• 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.

  by jwr
• Could you elaborate on this thought? MCP vs CLI feels very much like a Apples/Oranges comparison, without additional context.
  by narvidas
• CLI certainly is better than local MCP. But nowadays, most MCPs are remote and the comparison fall short, at the notable exception of `gh` in a coding environment. But having CLI already authenticated is not guaranted either!
  by timq
• I've been sitting in the same camp recently. We maintain both an internal MCP and CLI for our app which our devs use locally. The CLI so far feels like a much smoother experience both in terms of setup, control and performance.

  But i can see how MCP being able to plug into a remote agent that doesn't have terminal access is very useful. Seems like it's a best tool for the job conversation or am I missing some other advantage?

  by hoakiet98
• There is definitely some debate going on on mcp/cli/api etc, but is quite obvious that mcp is being adopted as standard for integrating third party applications to the major clients => chatgpt apps, claude connectors, mistral, cursor etc.. they all connect to external apps using mcp. Of course it's possible for you to tell claude to use some cli directly but it's much easier to connect the mcp with one click
  by tonxxd
• 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

  by NegativeLatency
• Not for every situation. CLI is great for coding agents (and I'd agree, far better in most cases than MCP). But it requires some execution runtime somewhere to actually run. So for app use cases where you don't want to build out your own tools for every integration, MCP can be a solid option.
  by dinkleberg
• Ciao Luigi! GJ team manufact!
  by orliesaurus
• congrats guys! how does the automated testing using ChatGPT/Claude clients work?
  by maxalbarello
• Very interesting, will keep you in mind.
  by Getchowned
• Looks great, congrats Pietro & Luigi!
  by mmarcelline
• thanks!
  by pzullo
• stopped using mcp and mostly using skills now. can't understand what this product does or how it could help me.
  by pacman1337
• To me that’s a bit like saying I started using shell scripts and stopped calling APIs - skills are playbooks, mcps are ‘documented APIs’ for the ai to call.

  Yes I can’t figure out exactly what it does…

  by maxrev17
• Looks great! Congratulations on the launch, guys!
  by abewheeler
• thanks!
  by pzullo
• Huge congrats to the team on the official launch of Manufact!
  by oliviajuwono
• we have so many problems with MCP related to auth, scopes etc... how do you guys help solve that?
  by ayushrodrigues
• Can you get into the specifics of the problems you currently experience with MCP? I'd love to learn more.
  by erdos_2
• with our SDK we provide many adapters to popular authentication providers which basically provision oauth on your server in one line of code, here the docs https://docs.mcp-use.com/typescript/server/authentication/in...

  also we ship templates for you to get started https://manufact.com/templates

  by pzullo
• One issue i saw related to scopes is the offline_access one that causes frequent reauthenticate request from the client. for example codex has this bug (https://github.com/openai/codex/issues/20503). many servers solve this with some workarounds or increasing the token life. In v2 of mcp-use coming end of the month there should be a builtin way to deal with buggy clients so the server remains connected.
  by tonxxd
• Really excited to use this, i'm migrating off stainless after anthropic bought them, we have to be off by september
  by ICodeSometimes
• happy to onboard you personally! We did a stainless migration two days ago :)
  by pzullo
• Love it guys! Also working deep in the MCP space we’ve used manufact right since the start. Great product, team and new release! Congrats
  by elliotgarreffa