This topic was automatically generated from Slack. You can find the original thread here.
Hey guys, we are on the Connect subscription plan and are facing issues with most MCPs and their actions for some time now. My question is, where can I find the roadmap plan for Pipedream connect? We are facing problems with the most common MCPs like Google Calendar, Meets, all databases etc. Most MCPs we use have missing actions due to which the apps are not usable at all by the agent to be effective.
I want to get an idea on what we can expect in the future and should my team contribute to these issues? Are they known etc etc. Any help here would be appreciated. Thanks!
Hey Ali, can you provide more specifics? We’re constantly adding tools to integrated apps in our MCP server, so let us know what you’re looking for and we can get it prioritized if it isn’t already.
Thanks for the response and sharing the project board. So some of the most commonly used apps have missing actions, just to name a few:
• Google Calendar does not have current time action due to which meetings scheduled are somewhere in 2024. Even if we add our own tool, the event scheduling action has datetime errors and only quick schedule works.
• Linear’s own MCP has the action to get team members but pipedream connect app does not have it due to which assigning an issue is not possible.
There are many more similar issues due to which creating effective workflows becomes a challenge. What is the best way to raise these and get them fixed at-least for the apps that are popular? thanks again for your response.
With 4000+ plus issues in the backlog, what kind of turn around time can I expect? Just for these 2 tasks lets say; add get_current_time action in Google Calendar and use Linear’s official MCP instead of the one you guys made?
Since our product directly depends on Pipedream as of now for external MCPs, getting these timelines would help us communicate better with our customers. Thanks and looking forward to your response.
Hi , you can submit a new action request and wait for Pipedream team to implement new action - this is subject for prioritization from Pipedream team.
If the timeline is sensitive to you, you can submit a PR to have the Component dev team review directly. This should shorten the time needed to have the action available. See this document here: Using Custom Tools - Pipedream
A get_current_time tool for Google Calendar is a good idea. And re: using Linear’s official MCP instead of Pipedream’s, what is the question there? How would you envision that working?
Re: “use Linear’s official MCP instead of Pipedream’s”
what I mean is: Context: Pipedream’s MCP tools are generated from Pipedream’s registry of pre-built actions (Connect-powered), so if an app’s action coverage is missing / schemas drift, the MCP toolset drifts too. Linear specifically: Linear ships an official remote MCP server (SSE + HTTP) with OAuth, centrally hosted/managed by Linear (https://mcp.linear.app/sse, https://mcp.linear.app/mcp).
In practice, Linear’s tool surface is closer to “ground truth” (their own product), and we’ve found it covers key gaps (e.g., fetching users/teammates for assignment) more reliably than the current Connect toolset.
How I’d envision this working in Pipedream (two viable approaches):
“Parity / sync” approach (simplest): Keep Pipedream’s MCP server as-is, but update the Linear Connect action registry to reach functional parity with Linear’s official MCP tools (e.g., add the missing “list users / team members” actions, fix schema/parameter mismatches). This keeps your current architecture (actions → tools) intact.
“Upstream official MCP adapter” approach (more strategic): Allow a Connect integration to optionally be backed by an official remote MCP endpoint (where available), so Pipedream can:
pull tools/list from the upstream server, proxy tools/call through Pipedream (still keeping user credential handling on the Pipedream side),
and expose either (a) upstream tool names directly or (b) mapped/aliased names for backward compatibility.
This second approach becomes more valuable as more vendors publish official MCP servers (Google just announced fully-managed remote MCP servers for Google/Google Cloud services, starting with Maps/BigQuery/GCE/GKE and expanding over time).
For our immediate need: I’m happy with approach #1 for Linear if it’s faster (add missing “team/user” actions + fix schemas). If you’re open to it, we can submit a PR (or detailed action-request issues) targeting just the high-usage gaps first.
:skin-tone-2: