PipedreamHQ / PipedreamHQ/pipedream
[FEATURE] MCP for User-Generated Workflows
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
I am building with agents. The fact that you have MCP servers for all your API integrations is a game-changer.
However, when I build a workflow as a tool for an agent, I will have to put it in a tool registry - lightweight at first, a DIY MCP later.
If you a) defined how we can make a workflow that qualifies for an MCP, b) enabled MCP for these workflows, and c) ensured that agents can make their own MCP-compliant workflows - well that would be tremendous.
From both a technical and business perspective, you would pull a jujitsu move analogous to the time Amazon stopped being a store and started hosting stores. You'd get out of your own way. You'd have a Cambrian explosion of tools.
And I wouldn't have to turn my tool registry into an MCP.
Contributor guide
Assessment
This issue has not been assessed yet.