What causes "Pipedream MCP error: ${error.message ?? 'Unknown error'}" in FlowiseAI/Flowise?

Read the appended underlying message to identify the real cause.

FlowiseAI/Flowise · error · Error

Pipedream MCP error: ${error.message ?? 'Unknown error'}

Error message

Pipedream MCP error: ${error.message ?? 'Unknown error'}

What it means

The final catch-all in getTools: any error from toolkit.initialize()/tool building not matched by the 404/401/timeout/ECONNREFUSED branches is re-thrown prefixed with 'Pipedream MCP error:' and the underlying message (or 'Unknown error' if absent).

Source

Thrown at packages/components/nodes/tools/MCP/Pipedream/PipedreamMCP.ts:359

            if (tools.length === 0) {
                throw new Error(`No tools available for the Pipedream app slug "${appSlug}". Please check your configuration.`)
            }

            return tools
        } catch (error: any) {
            if (error.message?.includes('404')) {
                throw new Error(`Pipedream app slug "${appSlug}" not found. Please verify the slug on mcp.pipedream.com.`)
            }
            if (error.message?.includes('401')) {
                throw new Error('Invalid Pipedream credentials. Please verify your Client ID and Client Secret.')
            }
            if (error.message?.includes('timeout') || error.message?.includes('ECONNABORTED')) {
                throw new Error('Connection to Pipedream MCP server timed out. Please check your network connectivity.')
            }
            if (error.message?.includes('ECONNREFUSED')) {
                throw new Error('Connection refused by Pipedream MCP server. The service may be temporarily unavailable.')
            }
            throw new Error(`Pipedream MCP error: ${error.message ?? 'Unknown error'}`)
        }
    }
}

module.exports = { nodeClass: Pipedream_MCP }

View on GitHub (pinned to abe4a8601a)

Solutions

Read the appended underlying message to identify the real cause.
If it indicates a server (5xx) error, retry after checking Pipedream status.
If it indicates a schema/parse error, verify toolkit and node versions are current.
Add temporary logging of the raw error object to capture stack/status not present in message.

Defensive patterns

Strategy: try-catch

Try / catch

try { await pipedream.getTools(nodeData, options) }
catch (e) {
    const m = e instanceof Error ? e.message : ''
    if (m.startsWith('Pipedream MCP error:')) {
        const detail = m.slice('Pipedream MCP error:'.length).trim()
        // classify: 5xx -> retry/incident; parse/schema -> version check
    }
}

Prevention

Log the full error object (status, stack) since the wrapped message may lose detail.
Keep the MCP toolkit and Pipedream node on current versions to avoid schema mismatches.
Add the underlying error code to the thrown message for faster triage.

When it happens

Trigger: An unexpected failure during MCP initialization or tool construction — e.g. SSE handshake error, JSON parse error, Zod schema error, or a 5xx from Pipedream that doesn't match the keyword checks.

Common situations: Pipedream returns 500; the SSE transport fails mid-stream; the toolkit throws an undocumented error type; partial/garbled response; unhandled edge case in createPipedreamTool before allSettled.

Related errors

AI-assisted analysis of FlowiseAI/Flowise@abe4a8601a (2026-08-12). Data as JSON: /api/errors/461fe0c9e100f327. Report an issue: GitHub.