FlowiseAI/Flowise · warning · Error

Connection to Pipedream MCP server timed out. Please check y

Error message

Connection to Pipedream MCP server timed out. Please check your network connectivity.

What it means

Catch-block branch: if the underlying error message includes 'timeout' or 'ECONNABORTED', the connection to the Pipedream MCP server (remote.mcp.pipedream.net) is reported as timed out.

Source

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

                createPipedreamTool(toolkit, t.name, t.description || t.name, t.inputSchema ?? { type: 'object', properties: {} })
            )
            const settled = await Promise.allSettled(toolPromises)
            const tools = settled.filter((r): r is PromiseFulfilledResult<Tool> => r.status === 'fulfilled').map((r) => r.value)

            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

1. Check network connectivity and latency from the server to remote.mcp.pipedream.net.
2. If behind a proxy, ensure it is configured and not stalling the SSE connection.
3. Retry; if intermittent, consider increasing the toolkit timeout if configurable.
4. Check Pipedream status for MCP endpoint degradation.

async function withRetry<T>(fn: () => Promise<T>, retries = 2): Promise<T> {
    for (let i = 0; ; i++) {
        try { return await fn() }
        catch (e) {
            if (e instanceof Error && /timed out|ECONNABORTED/i.test(e.message) && i < retries) { await delay(500 * (i + 1)); continue }
            throw e
        }
    }
}

When it happens

Trigger: toolkit.initialize() or a tool call exceeds the configured timeout while contacting remote.mcp.pipedream.net, producing an axios ETIMEDOUT/ECONNABORTED.

Common situations: Slow network; corporate proxy adding latency; Pipedream MCP server slow under load; very large tool lists; restrictive firewall causing TCP stalls rather than refusal.

Understand the failure class

• Timeouts: ETIMEDOUT, deadlines, and hung requests — what actually expires when a request times out.

Related errors

• Connection refused by Pipedream MCP server. The service may
• Invalid MCP Server Config: ${error}
• Failed to retrieve access token: Response missing access_tok
• Pipedream OAuth token request failed [${code}]: ${message}
• Pipedream app slug is required

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