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?
show comments
msencenb
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?
show comments
rgbrgb
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
show comments
pacman1337
stopped using mcp and mostly using skills now. can't understand what this product does or how it could help me.
elliotgarreffa
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
Getchowned
Very interesting, will keep you in mind.
ayushrodrigues
we have so many problems with MCP related to auth, scopes etc... how do you guys help solve that?
show comments
mmarcelline
Looks great, congrats Pietro & Luigi!
show comments
abewheeler
Looks great! Congratulations on the launch, guys!
show comments
connerBown
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.
show comments
maxalbarello
congrats guys! how does the automated testing using ChatGPT/Claude clients work?
oliviajuwono
Huge congrats to the team on the official launch of Manufact!
sampton
MCP is a deadend. CLI use is the future.
show comments
sebastiancrossa
we've been using manufact for months now. couldn't build mcps another way.
zxela
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.
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?
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?
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
stopped using mcp and mostly using skills now. can't understand what this product does or how it could help me.
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
Very interesting, will keep you in mind.
we have so many problems with MCP related to auth, scopes etc... how do you guys help solve that?
Looks great, congrats Pietro & Luigi!
Looks great! Congratulations on the launch, guys!
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.
congrats guys! how does the automated testing using ChatGPT/Claude clients work?
Huge congrats to the team on the official launch of Manufact!
MCP is a deadend. CLI use is the future.
we've been using manufact for months now. couldn't build mcps another way.
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.