Skip to main content

Connect OpenClaw

This guide uses OpenClaw's native MCP client configuration and a personal access token. For OAuth, contact support with your client's exact callback URI before connecting. See client compatibility.

Create a token with the MCP scope in Reconstruct Platform settings, as described in Personal access token. Set CR_RECONSTRUCT_MCP_TOKEN in your shell.

Add the server​

openclaw mcp add reconstruct \
  --url https://reconstruct.dev/mcp \
  --transport streamable-http \
  --header "Authorization: Bearer ${CR_RECONSTRUCT_MCP_TOKEN}"

This command saves the expanded token in OpenClaw's local configuration. Keep that file private and out of version control. Use streamable-http explicitly: OpenClaw's default remote transport is SSE, which is incompatible with Reconstruct's endpoint.

Check the connection​

openclaw mcp list
openclaw mcp doctor reconstruct --probe

Confirm that the live probe succeeds, then start a new agent session and ask OpenClaw to call list_products from reconstruct. Use a coding or messaging tool profile; minimal hides MCP tools. Check that your tool policy allows the server.

If an existing Gateway session still has the old configuration, restart the Gateway and start a new session. openclaw mcp reload only clears MCP runtimes in its own CLI process.

These commands manage mcp.servers in OpenClaw configuration. Installations using the separate mcporter integration manage their servers through config/mcporter.json and mcporter list. If your version lacks openclaw mcp add, update OpenClaw before following this guide.

See the official OpenClaw MCP registry guide and transport reference. If connection fails, check troubleshooting. Next, try the prompt examples.