Documentation Index
Fetch the complete documentation index at: https://pipedream.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
2026-04-15: Tool modes are no longer necessary with the latest Pipedream MCP server (
/v3 endpoint). Everything is now essentially tools-only, so the full tool schema is always returned.Tool modes
Pipedream MCP supports a few different methods for interacting with tools:- Sub-agent (default)
- Full config
- Tools only
Sub-agent
When using Pipedream MCP in sub-agent mode, all tools you expose to your LLM take a single input:instruction.
The Pipedream MCP server passes the instruction to an LLM to handle the configuration of the main tool using a set of agents with narrowly scoped sets of instructions and additional tools to aid in the configuration and execution of the top-level user prompt.
- The benefit with this approach is that sub-agent mode abstracts some of the complexity with handling things like remote options and dynamic props, especially for MCP clients that don’t automatically reload tools.
- However, one downside is that as a developer, you lose some of the control and observability in this model.
View the schema for the google_sheets-add-single-row tool in sub-agent mode
View the schema for the google_sheets-add-single-row tool in sub-agent mode
Full-config
Full-config mode enables support for loading and configuring dynamic props. This mode provides the most flexibility for tool configuration and is required for certain features like automatic app discovery. Usefull-config mode when you need:
- Greater control over tool configuration
- Support for dynamic props
- Automatic app discovery functionality
Configuring dynamic props
- Tools that use dynamic props can’t be configured in one shot, as the full prop definition isn’t known until certain inputs are defined.
- For example, the full set of props for
google_sheets-add-single-rowaren’t known until you configure thehasHeadersprop. Once you know if there’s a header row, you can retrieve the column names from the header row and make them available as props that can be configured. - As you call each tool, you should reload the available tools for the server to expose meta tools for configuration, such as
begin_configuration_google_sheets-add-single-row, which causes the rest of the tools to be removed and only expose tools relevant to the configuration.
Enabling full-config mode
To use full-config mode, you need to set 2 parameters:- Set the
toolModetofull-config - Pass a
conversationIdin order to maintain state for your end user’s conversation
View the schema for the google_sheets-add-single-row tool in full-config mode
View the schema for the google_sheets-add-single-row tool in full-config mode
Tools-only
To handle all tool configuration and calling directly, you should usetools-only mode.
View the schema for the google_sheets-add-single-row tool in tools-only mode
View the schema for the google_sheets-add-single-row tool in tools-only mode
Automatic app discovery
Automatic app discovery requires
full-config mode, which is not supported on the /v3 MCP server endpoint.full-config mode, you can enable Pipedream to automatically identify relevant apps from a given prompt by passing appDiscovery=true.
How it works
When app discovery is enabled:- Pipedream analyzes the incoming prompt to identify which apps are most relevant
- The initial tool call responds with an array of relevant apps
- When the client reloads its available tools, it has tools for the relevant apps
App detection examples
| User Input | Apps Detected |
|---|---|
| ”Send a message to the #general channel in Slack” | slack |
| ”Create a task in Notion and send a notification to Slack” | notion, slack |
| ”Add this email to my spreadsheet” | google_sheets, microsoft_excel, airtable_oauth, zoho_sheet, smartsheet |
| ”Schedule a meeting and update my CRM” | google_calendar, zoho_crm, hubspot |