I’m trying to use Canva’s MCP connector (https://mcp.canva.com/mcp) via OpenClaw ACP runtime, but MCP servers appear to be dropped during session setup.

Environment:

• OpenClaw: 2026.3.2 (85377a2)
• ACP backend: acpx
• Platform: macOS (Apple Silicon)

Observed behavior

• MCP configs can be set in external tools (Cursor/VS Code/Claude Desktop), but in OpenClaw ACP runtime path, MCP servers are not passed through.
• Inspection of bundled acpx runtime code shows mcpServers: [] hardcoded in session create/load paths.

Evidence

• File:
  /opt/homebrew/lib/node_modules/openclaw/extensions/acpx/node_modules/acpx/dist/cli.js
• Relevant lines (approx):
  • createSession(...) sends: mcpServers: []
  • loadSessionWithOptions(...) sends: mcpServers: []

Expected behavior

OpenClaw ACP runtime should allow configuring MCP servers (globally or per agent/session) and pass them into ACP session setup.

Example desired server:

• command: npx
• args: ["-y", "mcp-remote@latest", "https://mcp.canva.com/mcp"]

Actual behavior

MCP server list is always empty in runtime session setup, so Canva MCP connector cannot be used from OpenClaw main ACP runtime.

Impact

• Blocks Canva MCP workflows (and likely other MCP integrations) directly from OpenClaw ACP sessions.
• Forces users to run MCP-enabled workflows in external clients only.

Requested fix

1. Add user-facing MCP server config for ACP runtime (global and/or per-agent/per-session).
2. Pass configured servers into newSession/loadSession instead of hardcoded empty arrays.
3. Optionally expose validation/logging to confirm active MCP servers for a session.