Live data from Hacker News

Launch HN: Manufact (YC S25) – MCP Cloud

manufact.com

31–40 of 81 posts

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

#31

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 dep…

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

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

#32

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

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

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

#33

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

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.

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

#35
post #24

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.

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?

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

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

#37
post #2

MCP is a deadend. CLI use is the future.

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

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

#38
post #24

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.

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?

[deleted]

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

#40
post #2

MCP is a deadend. CLI use is the future.

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?

Post reply on HN