user-1
April 9, 2026, 3:28pm
1
This topic was automatically generated from Slack. You can find the original thread here .
Hi team, is there any plan to pick this up?
opened 02:25PM - 29 Jan 26 UTC
enhancement
**Is your feature request related to a problem? Please describe.**
The current … Pipedream actions and MCP tool configs are not optimized for agent use.
Generic tool names and descriptions derived from component configurable_props, which are written for human workflow builders, not for LLM tool selection and parameter filling.
No alignment with official MCP servers published by providers (e.g. Notion MCP, Linear, Google-related MCPs), which are explicitly designed for agents: clearer tool names, better descriptions, and schemas that reduce hallucination and wrong calls.
Inconsistent coverage of "viral" apps: The most widely used apps (Notion, Linear, Google Calendar, Gmail, Slack, etc.) would benefit most from agent-optimized tool definitions, but today they use the same generic mapping as the rest of the registry.
So agents get a worse experience on the highest-value integrations.
**Describe the solution you'd like**
**Fork or copy actions and MCP configs from official MCPs**
For key providers (e.g. Notion, Linear, Google Apps), either:
**Option A:** Introduce "agent-optimized" variants of existing actions (or new actions) whose tool names, descriptions, and parameter schemas are copied/adapted from the official provider MCPs, so the Pipedream MCP server exposes agent-friendly tools while still using Pipedream auth and execution; or
**Option B:** Maintain a separate layer of "MCP config" (tool name, description, schema, annotations) that overrides or augments the component-derived tool definition when the app is used via MCP, without forking action implementation code.
**Prioritize the most viral / high-impact apps**
Start with a short list (e.g. Notion, Linear, Google Calendar, Gmail, Slack, GitHub) and explicitly optimize their actions and MCP configs for agents. Then expand based on usage and demand.
We are this close to changing our provider
user-1
April 9, 2026, 3:28pm
2
Yes, we’re actively working on better optimizing a lot of our existing tools to work more natively in agent implementations and are so far seeing very good results.
