We’re thinking about it the other way—we don’t think there’s a world in which you a client (chat GPT/Claude) will string workflows together.
However, we need to speed up our integrations in Gumloop and MCP may be a way to do just that. Instead of hand-coding each integration, we’d want to focus on an MCP layer that dramatically increases the number of integrations we can offer in Gumloop. And since we were going to build this layer anyway, open sourcing it speeds that up even more.
If we’re able to build a more reliable way to interact with MCP servers, we could add hundreds of integrations faster than we could ever imagine.
Basically MCP (and open sourcing guMCP) is a way for us to speed up the number of integrations in Gumloop (we’ll mark those integrations as being MCP generated).
@Wasay-Gumloop thanks for your answer, but it is still not clear to me. You talk about Gumloop. Do you mean the company or the platform. In other words … can we expect MCP’s being offered in nodes so we can use them in flows, or will it be a stand alone product next to the flows.
D
Ditto what @Donna said. Excited to see Gumloop make MCP’s a tool to use in flows since thats the main hiccup to using gumloop currently - very few integrations and limited node creation with gummie.