4 ms·

Agree, one MCP server per API doesn’t scale. With something like https://nango.dev https://nango.dev you can get a single server that covers 400+ APIs. Also h

Agree, one MCP server per API doesn’t scale. With something like https://nango.dev https://nango.dev you can get a single server that covers 400+ APIs. Also handles auth, observability and offers other interfaces for direct tool calling. (Full disclosure, I’m the founder)

neya 1y ago
Looks pretty cool, thanks for sharing!
czechdeveloper 1y ago
Nango is cool, but pricing is quite high at scale.
- rguldener 1y ago
  We offer volume discounts on all metrics. Email me on robin @ <domain> and happy to find a solution for your use case
- falcor84 1y ago
  There are quite a few competitors in this space, trying to figure the best way about this. I've been recently playing with the Jentic MCP server[0] that seems to do it quite cleanly and appears to be entirely free for regular usage. [0] https://jentic.com/ https://jentic.com/
saberience 1y ago
Why do you even need to connect to 400 APIs? In the end, MCP is just like Rest APIs, there isn't need for a paid service for me to connect to 400 Rest APIs now, why do I need a service to connect to 400 MCPs? All I need for my users is to be able to connect to one or two really useful MCPs, which I can do myself. I don't need to pay for some multi REST API server or multi MCP server.
- herval 1y ago
  Agentic automation is almost always about operating multiple tools and doing something with them. So you invariably need to integrate with a bunch of APIs. Sure, you can write your own MCP and implement everything in it. Or you can save yourself the trouble and use the official one provided by the integrations you need.
  - saberience 1y ago
    My point is though, that you don't need some 3rd party service to integrate hundreds of MCPs, it doesn't make any sense at all. An "agent" with access to 400 MCPs would perform terribly in real world situations, have you ever tried it? Agents would best with a tuned well written system prompt and access to a few, well tuned tools for that particular agents job. There's a huge difference between a fun demo of an agent calling 20 different tools, and an actual valuable use-case which works RELIABLY. In fact, agents with tons of MCP tools are currently insanely UNRELIABLE, it's much better to just have a model + one or two tools combined with a strict input and output schema, even then, it's pretty unreliable for actual business use-cases. I think most folks right now have never actually tried making a reliable, valuable business feature using MCPs so they think somehow having "400 MCPs" is a good thing. But they haven't spent a few minutes thinking, "wait, why does our business need an agent which can connect to Youtube and Spotify?"
- _boffin_ 1y ago
  People want to not think and throw the kitchen sink at problems instead of thinking what they actually need.

neya 1y ago

Looks pretty cool, thanks for sharing!

czechdeveloper 1y ago

Nango is cool, but pricing is quite high at scale.

rguldener 1y ago
We offer volume discounts on all metrics. Email me on robin @ <domain> and happy to find a solution for your use case
falcor84 1y ago
There are quite a few competitors in this space, trying to figure the best way about this. I've been recently playing with the Jentic MCP server[0] that seems to do it quite cleanly and appears to be entirely free for regular usage. [0] https://jentic.com/ https://jentic.com/

saberience 1y ago

Why do you even need to connect to 400 APIs? In the end, MCP is just like Rest APIs, there isn't need for a paid service for me to connect to 400 Rest APIs now, why do I need a service to connect to 400 MCPs? All I need for my users is to be able to connect to one or two really useful MCPs, which I can do myself. I don't need to pay for some multi REST API server or multi MCP server.

herval 1y ago
Agentic automation is almost always about operating multiple tools and doing something with them. So you invariably need to integrate with a bunch of APIs. Sure, you can write your own MCP and implement everything in it. Or you can save yourself the trouble and use the official one provided by the integrations you need.
- saberience 1y ago
  My point is though, that you don't need some 3rd party service to integrate hundreds of MCPs, it doesn't make any sense at all. An "agent" with access to 400 MCPs would perform terribly in real world situations, have you ever tried it? Agents would best with a tuned well written system prompt and access to a few, well tuned tools for that particular agents job. There's a huge difference between a fun demo of an agent calling 20 different tools, and an actual valuable use-case which works RELIABLY. In fact, agents with tons of MCP tools are currently insanely UNRELIABLE, it's much better to just have a model + one or two tools combined with a strict input and output schema, even then, it's pretty unreliable for actual business use-cases. I think most folks right now have never actually tried making a reliable, valuable business feature using MCPs so they think somehow having "400 MCPs" is a good thing. But they haven't spent a few minutes thinking, "wait, why does our business need an agent which can connect to Youtube and Spotify?"
_boffin_ 1y ago
People want to not think and throw the kitchen sink at problems instead of thinking what they actually need.