Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Zapier MCP via @ownid/mcp-remote fails in OpenClaw bundle MCP with MCP error -32001: Request timed out [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#57969•Fetched 2026-04-08 01:55:29
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
cnsandboxcnsandbox
Participants
cnsandboxcnsandboxleonardo-bolanosleonardo-bolanos
Timeline (top)
labeled ×2commented ×1cross-referenced ×1

I'm trying to use Zapier MCP in OpenClaw via a stdio bridge subprocess:

"mcp": {
  "servers": {
    "zapier": {
      "command": "npx",
      "args": [
        "-y",
        "@ownid/mcp-remote",
        "https://mcp.zapier.com/api/v1/connect?token=..."
      ]
    }
  }
}

OpenClaw recognizes the MCP server config, but Zapier tools never surface in sessions.

Error Message

Historical logs show:

  • using @zapier/mcp-integration:
    • failed to start server "zapier" ... McpError: MCP error -32000: Connection closed
  • using @ownid/mcp-remote:
  • Tools do not appear in control-ui/webchat or Telegram sessions.

Root Cause

I'm trying to use Zapier MCP in OpenClaw via a stdio bridge subprocess:

"mcp": {
  "servers": {
    "zapier": {
      "command": "npx",
      "args": [
        "-y",
        "@ownid/mcp-remote",
        "https://mcp.zapier.com/api/v1/connect?token=..."
      ]
    }
  }
}

OpenClaw recognizes the MCP server config, but Zapier tools never surface in sessions.

Code Example

"mcp": {
  "servers": {
    "zapier": {
      "command": "npx",
      "args": [
        "-y",
        "@ownid/mcp-remote",
        "https://mcp.zapier.com/api/v1/connect?token=..."
      ]
    }
  }
}

---
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Summary

I'm trying to use Zapier MCP in OpenClaw via a stdio bridge subprocess:

"mcp": {
  "servers": {
    "zapier": {
      "command": "npx",
      "args": [
        "-y",
        "@ownid/mcp-remote",
        "https://mcp.zapier.com/api/v1/connect?token=..."
      ]
    }
  }
}

OpenClaw recognizes the MCP server config, but Zapier tools never surface in sessions.

Environment

  • OpenClaw: 2026.3.28
  • Install method: pnpm
  • OS: macOS
  • Node: 25.6.1

Observed behavior

Historical logs show:

  • using @zapier/mcp-integration:
    • failed to start server "zapier" ... McpError: MCP error -32000: Connection closed
  • using @ownid/mcp-remote:
  • Tools do not appear in control-ui/webchat or Telegram sessions.

What I ruled out

  • wrong launcher:
    • @zapier/mcp-integration appears to be the wrong runtime shape here
  • missing config:
    • mcp.servers.zapier is present and loaded
  • stale runtime:
    • OpenClaw was updated/restarted during testing
  • conflicting auth config:
    • simplified config to avoid malformed/custom header issues

Source-level finding

From the installed OpenClaw code, bundle MCP appears to support only stdio MCP servers in this path. The relevant bundle code:

  • rejects config with only url as:
    • only stdio MCP servers are supported right now
  • launches MCP servers via StdioClientTransport
  • then does client.connect(transport) and tool listing So remote Zapier MCP appears to depend on the stdio bridge subprocess, and that startup/list-tools phase is where it fails.

Expected behavior

If @ownid/mcp-remote is used as the MCP bridge subprocess, Zapier MCP tools should materialize in OpenClaw sessions.

Actual behavior

OpenClaw attempts to start the MCP server but fails during initialization / tool discovery with timeout, and no tools surface.

Question

Is this:

  • a known limitation with stdio-bridged remote MCP servers,
  • a startup timeout bug in bundle MCP,
  • or an unsupported transport combination that should be documented more clearly?

Steps to reproduce

Configure Openclaw with MCP Server Link

Expected behavior

Zapier MCP server to surface without any error on Openclaw

Actual behavior

Observed behavior

Historical logs show:

  • using @zapier/mcp-integration:
    • failed to start server "zapier" ... McpError: MCP error -32000: Connection closed
  • using @ownid/mcp-remote:
  • Tools do not appear in control-ui/webchat or Telegram sessions.

OpenClaw version

2026.3.28

Operating system

OS: macOS 25.6.1

Install method

No response

Model

ChatGPT Codex 5.3

Provider / routing chain

openclaw -> Zapier

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To resolve the issue with Zapier MCP tools not surfacing in OpenClaw sessions, we need to adjust the configuration and potentially modify the startup process of the MCP server. Here are the steps:

  1. Update MCP Server Configuration: Ensure that the mcp configuration in OpenClaw is correctly set up to use @ownid/mcp-remote with the stdio bridge subprocess.
  2. Increase Timeout: Modify the timeout value for the MCP server startup to prevent timeouts during the tool discovery phase. This can be done by adding a timeout option to the mcp configuration.
  3. Verify Stdio Bridge Subprocess: Confirm that the stdio bridge subprocess is correctly configured and launched for the Zapier MCP server.

Example configuration update:

"mcp": {
  "servers": {
    "zapier": {
      "command": "npx",
      "args": [
        "-y",
        "@ownid/mcp-remote",
        "https://mcp.zapier.com/api/v1/connect?token=..."
      ],
      "timeout": 30000 // increase timeout to 30 seconds
    }
  }
}

Verification

To verify that the fix worked:

  1. Restart OpenClaw and check the logs for any errors related to the MCP server startup.
  2. Verify that the Zapier MCP tools are visible in the control-ui/webchat or Telegram sessions.

Extra Tips

  • Ensure that the @ownid/mcp-remote package is up-to-date and compatible with the OpenClaw version.
  • If issues persist, try increasing the timeout value or adjusting the MCP server configuration to use a different transport method.
  • Refer to the OpenClaw documentation for more information on configuring MCP servers and troubleshooting common issues.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Zapier MCP server to surface without any error on Openclaw

#api#GPU compatibility#latency issue#model loading#dependency error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Zapier MCP via @ownid/mcp-remote fails in OpenClaw bundle MCP with MCP error -32001: Request timed out [1 comments, 2 participants]