Launch HN: Manufact (YC S25) – MCP Cloud (manufact.com)

67 points by pzullo 3 hours ago

Hi HN, we are Pietro and Luigi, cofounders of Manufact (https://manufact.com), a cloud for MCP apps and servers. We used to be called mcp-use, and still build open source SDKs for MCP under that name: https://github.com/mcp-use/mcp-use. We did a Show HN about that last year: https://news.ycombinator.com/item?id=44747229.

Today we want to tell you about our cloud product, Manufact, which is to mcp-use as Vercel is to Next.js. Manufact is an MCP vertical cloud designed for dev teams putting MCP Apps and servers in production.You can ship, iterate on, test and monitor your MCPs, and get them ready for the store submissions. All with the best developer and agent experience in mind.

Here is a demo video of the product: https://www.youtube.com/watch?v=R2rbr5OT9LI.

We have been working on MCP since April 2025. Our first focus was making it easy to build agents that could use any MCP server, and a lot of people started using our SDKs. Then the harness revolution kicked off: Claude Code, Claude Cowork, ChatGPT, Codex, OpenCode started shipping agent harnesses that made most standalone agent frameworks redundant. That pushed us to the other side of the connection, the servers. If agents were going to consolidate into a few harnesses, then first-class integration with the rest of a company's systems (i.e. MCP) would become the thing that mattered, so we started building up our server SDKs.

Then in succession:

1. Oct 2025. ChatGPT Apps SDK. OpenAI brings app UIs to ChatGPT, built on top of MCP and the work of mcp-ui. 2. Late 2025. The stores open. ChatGPT starts accepting app submissions, Claude grows its connector directory with selected partners. 3. Jan 2026. MCP Apps becomes official. SEP-1865 merges as the first MCP extension (io.modelcontextprotocol/ui): one UI standard any host can render.

Today, all the major clients fully support MCP and are opening marketplaces of reviewed MCPs that can be one click installed. All major tech companies have an MCP server, and many of those are reporting that already 15+% of their usage comes from their MCP, and we start to have a good way to distribute them just now.

MCP can return fully interactive UIs. So companies can (1) display data in more meaningful ways to their users (e.g. analytics, ecommerce) and (2) display their branding in some of the most used products on the planet (ChatGPT, Claude etc). Numbers: an engineer at Amplitude reported that their MCP saw a 2x increase in retention after adding UI to their MCP.

Clients (Claude, ChatGPT, Cursor) are starting to dynamically present MCP servers/apps to users, based on their intent. Products will be organically discovered on the chats!

We feel that MCP is reaching its maturity moment. Now that MCPs are starting to be easy to install and discover, there is going to be a huge incentive for users to use them and for companies to create them:

1 - Most work is already done from AI chats, this is not going to stop, MCP gives you a way to interact with products without manually using their dashboards.

2 - MCP allows you to bring the context together in one place: you can read an email, create a ticket while plugged into the source code of your product, or your knowledge base. Aggregation of products that was not possible before, will happen in the chat, orchestrated by increasingly intelligent models.

If AI apps (Codex, Claude Desktop) are the new browsers, as PG said in a recent tweet https://x.com/paulg/status/2069080429236191504, then MCPs are the new websites.

But there is a catch:

- Submission process on the stores is still quite tricky, manual and takes up valuable time. - Hardly anybody knows how to design a good MCP: most of them are 1:1 proxies of the API and are abandoned, since being one shotted a few months ago. - The MCP Spec advances quickly and it is not easy to keep track of the changes, and what they mean for your server. - Auth is still a mystery for most teams (API key in the URL ???). - Most companies are not even aware that MCPs can return interactive UIs. - Clients still have to consolidate behavior, some do dynamic tool discovery, some don't, some persist authentication properly some don't.

We built Manufact and mcp-use to solve these problems. Our SDKs help them build good MCPs, our inspector helps them test locally, and our cloud helps them ship/publish and monitor them in production.

To deploy on Manufact you just need to connect a Github app, pick the repo, we'll detect the framework you are working with and get you a live MCP url as soon as possible.

In our platform, that live URL will be used to give you a chat where you can try/debug your MCP immediately and share it with your team. If you push an update on a new experimental branch, you'll be able to test that as well thanks to preview deployments.

Once your server is ready to go live, we help you make sure that it does not break. You can configure automated tests that will take your MCP server, install it in ChatGPT and Claude and test it. We do not test the model, we test the client (model + harness). This way you reliably know if your server breaks where people use it.

Since publishing on the store is a major distribution unlock for companies (your MCP can be dynamically discovered and one click installed across Claude products, and ChatGPT), we collected a set of requirements that will keep your submission from being rejected. You check this locally before going through the actual review process.

Once your server is live, you'll want to understand how it is used. Our analytics are designed for MCP, so you'll know how many users are hitting your MCP, how many tool calls you receive, from which client.

You can try out https://manufact.com for free today. We have usage-based pricing and on our free account we give free credits for you to try it out. If you have an MCP already, just connect your Github repo and deploy, if not you can build one using our skill and SDKs pretty simply (we will guide you in the onboarding).

We would love to hear feedback about the product in the comments, and hear thoughts from everyone about MCP. Thanks! :)

zxela 38 minutes ago

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.

pzullo 15 minutes ago

noted! thanks for the feedback, will be gone soon

Brainspackle an hour ago

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?

pzullo an hour ago

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

msencenb 2 hours ago

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?

pzullo an hour ago

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

rgbrgb 2 hours ago

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

pzullo 2 hours ago

+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

nijave an hour ago

Yeah MCPs are easier to distribute.

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

Getchowned 32 minutes ago

Very interesting, will keep you in mind.

pacman1337 2 hours ago

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

elliotgarreffa an hour ago

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

mmarcelline an hour ago

Looks great, congrats Pietro & Luigi!

pzullo an hour ago

thanks!

ayushrodrigues 2 hours ago

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

tonxxd an hour ago

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.

harijoe 2 hours ago

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.

pzullo an hour ago

we support deploying Skybridge too https://manufact.com/blog/mcp-app-with-skybridge ! saw that you work for the company that is developing that, usually on HN to keep it honest you want to disclose that

dotancohen 2 hours ago

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?

pzullo an hour ago

pzullo an hour ago

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

erdos_2 2 hours ago

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

abewheeler an hour ago

Looks great! Congratulations on the launch, guys!

pzullo an hour ago

thanks!

connerBown 2 hours ago

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.

stingraycharles 2 hours ago

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.

maxalbarello 2 hours ago

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

oliviajuwono 3 hours ago

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

sampton 3 hours ago

MCP is a deadend. CLI use is the future.

dinkleberg 2 hours ago

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.

sudb 2 hours ago

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.

hoakiet98 an hour ago

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?

tonxxd an hour ago

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

NegativeLatency 2 hours ago

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

timq 2 hours ago

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!

narvidas 3 hours ago

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

martinald 2 hours ago

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.

jwr 2 hours ago

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.

phpnode 2 hours ago

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

Catloafdev 2 hours ago

They serve two different purposes.

Edited*

dang 2 hours ago

> 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.

Catloafdev 2 hours ago

sebastiancrossa 2 hours ago

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