“What needs review in this configuration?”
Request a supported validation and inspect its findings before preparing a change.
AI Integrations / OpenClaw
NetConverter
for OpenClaw.
Bring network configuration checks and supported migrations into your OpenClaw workflow. Ask for the work. Inspect the evidence. Keep control of the change.
Local MCP bridge · NetConverter account and enabled access required
ON YOUR OPENCLAW GATEWAY HOST
CONNECT YOUR WORKSPACE
netconverter login --clerk
netconverter capabilities
netconverter connect openclawThen ask OpenClaw
“Validate demo-asa.cfg through NetConverter and explain what needs review.”
File pathNetConverter bridgeHosted job
Illustrative request. Use a synthetic file and a credential offering ASA validation. No live job is shown.
From a request to a review
Your assistant coordinates.
NetConverter does the job.
OpenClaw calls the local bridge with the requested operation and file path. The bridge transfers the selected file to NetConverter over HTTPS and returns the job information and permitted results.
- 01 / CHOOSE
Ask for a supported task
Validate, convert or optimize a configuration using the operations your NetConverter account offers.
- 02 / SUBMIT
Pass a file path
The bridge reads the selected file on the Gateway host and sends it directly to the service.
- 03 / INSPECT
Follow the evidence
Use the job ID to inspect status, findings and the checks that actually ran. Privacy settings control the assistant’s result view.
- 04 / REVIEW
Keep the final decision
Review downloaded artifacts and test the target. The terminal does not deploy configurations to devices.
Practical requests
Start with the questions
engineers already ask.
Use the assistant to navigate supported work and explain its evidence. The job’s deterministic status and unresolved findings remain visible.
“Convert this ASA export to a supported Palo Alto format.”
Check account capabilities and supply the required decisions. Review the output and warnings.
“What did this job actually verify?”
Ask for the report evidence, skipped checks and missing coverage, using the real job ID.
Data and control
Know what travels
through each connection.
Configurations go from the bridge to NetConverter for hosted processing. Default masked exposure limits the assistant’s results. Broader exposure requires a separate user choice.
Set OpenClaw’s own file policy too
The bridge does not govern OpenClaw’s independent file or exec tools. The setup guide explains the Gateway workspace, the printed policy guidance and result exposure. Connecting an MCP server alone does not establish those controls.
Read privacy and data flow →Before connecting
A few useful answers.
The integration uses the existing NetConverter CLI and hosted service.
Do I need a separate NetConverterClaw product?
No. NetConverter for OpenClaw uses the existing CLI’s local MCP bridge and your NetConverter account. You can keep using the terminal or other supported assistants.
Where do I install the CLI?
On the host running OpenClaw’s Gateway, with access to the intended workspace and credentials. A gateway on another machine cannot automatically use files from your laptop.
Does this run offline or deploy to my firewall?
Processing is hosted, so it needs a connection to NetConverter. The CLI downloads outputs for review; it does not deploy them to a device.
Which versions have been checked?
The published matrix records an October 22, 2026 test of OpenClaw 2026.10.6 with bridge 0.4.1. Current CLI 0.6.0 verification is still marked to verify. Start with a synthetic example and check the dated compatibility guide.
Connect one workspace
Put NetConverter tools
within OpenClaw’s reach.
Install the CLI, check your account’s capabilities and run a synthetic first task. Follow the guide from connection through evidence review.