alt.hn

7/2/2026 at 3:11:20 PM

Launch HN: Manufact (YC S25) – MCP Cloud

 https://manufact.com

by pzullo

7/2/2026 at 8:15:24 PM

Hey Luigi & Pietro, it's Matt from MCPJam (previously). So cool seeing you guys rock the space. Congrats on the launch!

Any apps you can share that are on the OpenAI apps store / Claude store that are built / hosted on Manufact?

by freestylematt

7/2/2026 at 7:58:35 PM

Cool. The main thing I like about MCP is the authentication story, particularly the standardisation around OAuth.

Because of that, I think it is often worth wrapping an API in an MCP server. I actually had to do this recently.

I have been working on an open-source project called crmkit.ai. I was not planning to add MCP support because the project already works in a very agent-native way, where the agent reads the `setup.md` file at the root of the server and then uses `curl`.

That works well for normal agents. It kind of works in claude.ai, although you need to allowlist the domain. It does not work on chatgpt.com because the sandbox does not allow arbitrary outbound web requests. It should work fine in Codex, Claude Code, etc. because those run locally.

For ChatGPT, I was forced to write an MCP server. But because this is supposed to be an agent-first CRM, I thought that instead of exposing hundreds of small tools and polluting the context, why not expose a single tool called `request`, where the LLM writes the actual HTTP request?

That should work, right?

It does not. ChatGPT effectively forces you to unwrap the entire API into lots of small tools, because each one may need to be authorised separately.

Anyway, I ended up doing it, but needless to say, the design feels wrong. It would have been much better if the MCP server could expose a single `request` tool and keep the context tight.

The single-tool concept does work. We use crmkit internally with fully autonomous agents, and I even use it personally as a productivity tool.

The moral of the story is that MCP has great authentication but I rather not use it if I can. If I need to use it I would prefer to expose a single tool that write the raw request even-though it feels like a hack and it does not work across all chat systems.

I hope this anecdote helps.

by _pdp_

7/2/2026 at 4:55:27 PM

Having to sign up to browse available MCPs stopped me dead in my tracks and made me close the tab. I won't be the only one. Perhaps consider allowing people to browse more of the site before you try to force a signup on them?

by Brainspackle

7/2/2026 at 5:08:32 PM

hey thanks for the feedback, we do not really offer a "set" of pre made MCPs that we could show pre signup, unfortunately our platform requires you to deploy something to use it - we try to give an overview of all the features in our "Platform" section in the navbar on top

by pzullo

7/2/2026 at 8:00:22 PM

Really excited to use this, i'm migrating off stainless after anthropic bought them, we have to be off by september

by ICodeSometimes

7/2/2026 at 4:06:43 PM

I am really impressed with your demo video, particularly the analytics, logs, and test suite features.

I'm a target customer where I have a few curious customers, but I'm not fully ready to roll it out yet across the customer base. One thing that's stopping me, what does credits mean on your pricing page? And what is the pay as you go price after you hit your limit? I would need to be able to budget this before I deploy.

The second piece - we already have a CLI, which is great for terminal based agents and what we will continue to recommend. What we really want, and I think is what you are offering, is basically an easier way to deploy a 'remote connector' to use Claude lingo so that normal users with the claude/chatgpt app can just use our MCP. Can you point me to guidelines or the right place in your open source templates to understand how I would best handle auth (or the tradeoffs in each) during the initial build phase of the MCP server?

by msencenb

7/2/2026 at 4:48:39 PM

thank you so much we have put a lot of love into our product!

pricing: we offer several credit based products that have different cost - requests, build minutes, eval runs, checklist all have different unit cost the breakdown is here https://docs.manufact.com/dashboard/billing thanks for pointing out that it should be more transparent!

auth: we published a few blogs https://manufact.com/blog/oauth-mcp https://manufact.com/blog/authentication

+ lots of auth templates you can start from https://manufact.com/templates

by pzullo

7/2/2026 at 7:11:07 PM

Question: I have an MCP server that is working well with Auth (Google Only), running on vercel. What benefit would I get from running it on manufact?

On monetizing my MCP... How do the different MCP "Stores" handle this? Do some take a cut? Or are they agnostic? Does manufact help with monetization?

by mrtimo

7/2/2026 at 7:22:41 PM

Thanks for the comment! Vercel is a generic cloud provider, so you won’t get any of the MCP specific features (listed in the post) and development experience - monetization is still not regulated by the protocol, so people would pay for your product before using your MCP, then you can charge based on subscription or usage as usual!

Do you use MCP-handler for your MCP ?

by pzullo

7/2/2026 at 3:53:04 PM

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

by rgbrgb

7/2/2026 at 4:45:12 PM

Yeah MCPs are easier to distribute.

In my experience, they also work better with dumber models than CLIs (which saves money)

by nijave

7/2/2026 at 4:35:09 PM

+1 !! Thanks for putting it so clearly, also CLIs and REST have their space in some applications, I think MCP is a way to organize them and distribute them better

by pzullo

7/2/2026 at 4:42:39 PM

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

7/2/2026 at 6:33:51 PM

Ciao Luigi! GJ team manufact!

by orliesaurus

7/2/2026 at 3:55:46 PM

we have so many problems with MCP related to auth, scopes etc... how do you guys help solve that?

by ayushrodrigues

7/2/2026 at 4:53:15 PM

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

7/2/2026 at 4:22:12 PM

You may want to have a look at Skybridge, a TypeScript framework designed to build MCP servers and MCP Apps, with a recent emphasis on making authentication easy.

by harijoe

7/2/2026 at 4:29:21 PM

TypeScript, for all its benefits, still feels like a toy or project language. I'd love to see a Rust, C++, or even a Go library for such purpose.

I'd love for people with experience to break me of this negativity towards TypeScript. Anybody?

by dotancohen

7/2/2026 at 4:56:13 PM

a few thoughts for MCP: - typescript "runs" in the browser, which is very handy to develop browser side MCP Clients - for similar reasons it is the only real option to develop UIs for MCP Apps for instance

not particularly related to MCP: as most products rely on external APIs provided by the labs (ChatGPT wrapper as we used to call them) frontend languages become more important

by pzullo

7/2/2026 at 4:09:46 PM

Can you get into the specifics of the problems you currently experience with MCP? I'd love to learn more.

by erdos_2

7/2/2026 at 6:28:52 PM

MCP is a protocol, that's all.

Saying MCPs are the new websites is like saying "SOAP" is the new websites, or "REST" is the new websites.

MCP is basically the AI equivalent of a REST API, it's not a product anymore than JSON is a product or XML is a product.

by saberience

7/2/2026 at 5:37:07 PM

Very interesting, will keep you in mind.

by Getchowned

7/2/2026 at 3:52:36 PM

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.

by connerBown

7/2/2026 at 3:57:03 PM

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.

by stingraycharles

7/2/2026 at 4:39:04 PM

Looks great! Congratulations on the launch, guys!

by abewheeler

7/2/2026 at 5:12:03 PM

thanks!

by pzullo

7/2/2026 at 4:56:38 PM

Looks great, congrats Pietro & Luigi!

by mmarcelline

7/2/2026 at 5:12:11 PM

thanks!

by pzullo

7/2/2026 at 3:56:18 PM

stopped using mcp and mostly using skills now. can't understand what this product does or how it could help me.

by pacman1337

7/2/2026 at 7:04:33 PM

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

7/2/2026 at 4:04:22 PM

congrats guys! how does the automated testing using ChatGPT/Claude clients work?

by maxalbarello

7/2/2026 at 3:37:17 PM

Huge congrats to the team on the official launch of Manufact!

by oliviajuwono

7/2/2026 at 4:33:56 PM

we've been using manufact for months now. couldn't build mcps another way.

by sebastiancrossa

7/2/2026 at 3:29:50 PM

MCP is a deadend. CLI use is the future.

by sampton

7/2/2026 at 3:40:39 PM

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

7/2/2026 at 3:43:54 PM

Also, in my opinion, it's much easier to build a good MCP interface than it is to build a good CLI interface - and afaik there's support for MCP tools to return things like images from an MCP tool call directly to the calling LLM that is a bit tricker to do via CLI.

by sudb

7/2/2026 at 3:47:58 PM

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

7/2/2026 at 6:24:17 PM

MCP makes token use WORSE, not better.

by saberience

7/2/2026 at 7:05:08 PM

Not if you use mcplexer.com ;)

by maxrev17

7/2/2026 at 5:07:22 PM

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

7/2/2026 at 8:08:25 PM

[dead]

by scritty-dev

7/2/2026 at 4:57:10 PM

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

7/2/2026 at 4:08:36 PM

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

7/2/2026 at 3:36:53 PM

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

by narvidas

7/2/2026 at 3:49:06 PM

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.

by martinald

7/2/2026 at 8:22:24 PM

Yep, that was exactly my point with the ask to elaborate.

MCPs and CLIs are two wholly different things. Contrasting them feels even confusing vague than comparing Skills vs MCPs, which would also be wrong. The latter two are also very much a Apples vs Oranges discussion and serve different purposes.

I agree with @martinanld that MCPs, especially with the advent of EMA, are a completely different beast thanks to a structured way for auth and access control.

by narvidas

7/2/2026 at 3:48:46 PM

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

7/2/2026 at 3:42:35 PM

cached thought. running CLIs is impractical and expensive in many environments and a hell of a lot less secure than using MCP

by phpnode

7/2/2026 at 3:43:05 PM

They serve two different purposes.

Edited*

by Catloafdev

7/2/2026 at 3:46:58 PM

> 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.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.

by dang

7/2/2026 at 3:50:17 PM

Apologies, I appreciate you posting this!

by Catloafdev

7/2/2026 at 5:30:18 PM

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

7/2/2026 at 5:53:13 PM

noted! thanks for the feedback, will be gone soon edit: gone

by pzullo

7/2/2026 at 3:44:51 PM

[dead]

by jsmudda