Sign in Request access
Skip to content

AI integrations

Connect NetConverter to OpenClaw

Give OpenClaw access to supported NetConverter jobs through the local terminal bridge.

Updated November 2, 2026 · Terminal guides: CLI 0.7.0

Prepare the Gateway host

OpenClaw starts local MCP servers from its Gateway process. Install NetConverter CLI and sign in on that same host, with access to the intended workspace. A path on your laptop is not automatically available to a gateway running elsewhere.

You need an enabled NetConverter account, MCP access and a supported job type. Use a synthetic configuration for the first run. See the OpenClaw integration overview for the workflow.

Connect the bridge

Open a terminal in the folder that holds the demo configuration, then run:

netconverter login --clerk
netconverter capabilities
netconverter connect openclaw --print
netconverter connect openclaw

The preview shows what will change. Confirm the final command only after checking the workspace. The connection uses OpenClaw’s own MCP registration command and probes the bridge. If OpenClaw is not on PATH, the CLI prints a manual configuration block.

Set the file boundary

netconverter privacy status
netconverter privacy apply --client openclaw

The second command prints the suggested OpenClaw tool policy; it does not apply it. Review and apply the relevant policy on the Gateway host, then restart the Gateway. Keep OpenClaw’s own file and exec tools from reading the configuration workspace. Connecting the bridge alone does not restrict those independent tools.

Default masked exposure limits the bridge results. Higher exposure requires a confirmation typed in a terminal. Read the complete data-flow and exposure guide.

Try one supported task

  1. Ask OpenClaw to list its NetConverter tools and report the account capabilities.
  2. For a credential offering ASA validation, ask: “Validate demo-asa.cfg through NetConverter. Use the file path; do not read its contents into this conversation.”
  3. Follow the returned job ID and ask what the findings actually establish.
  4. Review the report and files yourself. Use /activity in the NetConverter app to inspect bridge metadata.

This instruction guides the assistant; actual file-access enforcement comes from its tool policy. No prompt alone establishes the boundary.

Compatibility and limits

The published matrix records an OpenClaw 2026.10.6 / bridge 0.4.1 tester run on October 22, 2026. It marks current-release verification as still to verify. These setup steps describe the implemented CLI 0.6.0 integration, not a new certification of every OpenClaw version or operating system.

For a headless Gateway, ensure its environment can reach the credential store. If an encrypted credential file is used, the bridge needs its passphrase through the supported environment or secret-file setting. See credential troubleshooting.

Remove the connection

netconverter connect openclaw --remove

This removes the registered bridge. Review any tool-policy changes separately; configuration files and downloaded artifacts remain yours.

Source and release context: OpenClaw setup · Dated test evidence · Privacy controls