FlowiseAI/Flowise · warning · Error

Connection refused by Pipedream MCP server. The service may

Error message

Connection refused by Pipedream MCP server. The service may be temporarily unavailable.

What it means

Catch-block branch: if the underlying error message includes 'ECONNREFUSED', the Pipedream MCP server actively refused the TCP connection, reported as the service being temporarily unavailable.

Source

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

            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. Verify https://remote.mcp.pipedream.net is reachable from the server (curl/TCP test).
2. Check Pipedream status page for an active incident.
3. Retry after a short wait; if persistent, inspect DNS resolution.
4. Ensure no firewall rule is refusing outbound 443.

try { await pipedream.getTools(nodeData, options) }
catch (e) { if (e instanceof Error && e.message.includes('Connection refused')) { /* check Pipedream status, retry shortly */ } }

When it happens

Trigger: Connection attempt to remote.mcp.pipedream.net is refused at the TCP layer — typically a transient outage, wrong port/host due to misconfiguration, or a network path that drops the TLS handshake.

Common situations: Pipedream MCP endpoint down or restarting; DNS pointing to a dead endpoint; local/network egress policy refusing the port; extremely rare given it is a managed HTTPS endpoint.

Understand the failure class

• Connection failures: ECONNREFUSED, ECONNRESET, and friends — why connections get refused, reset, or dropped.

Related errors

• Connection to Pipedream MCP server timed out. Please check y
• 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/23cd34f2b1a92556. Report an issue: GitHub.