Convert OpenClaw to .0n
Export your OpenClaw manifests, Claw configs, and MCP bridges. Convert to portable .0n workflows with 1,589 tools.
Level Up from OpenClaw
OpenClaw got you started. Now take your agents to the next level with the .0n ecosystem.
Limited Ecosystem
OpenClaw's tool and service ecosystem is still growing. 0nMCP offers 1,589 ready-to-use tools across 102 services today.
No Standard Format
Claw configs use a proprietary format with no interoperability. The .0n standard works across 7 AI platforms.
Bridge Complexity
MCP bridge configurations require manual setup for each service. 0nMCP handles connections automatically with built-in service adapters.
Scale Limitations
Running multiple agents with OpenClaw requires complex orchestration. 0nMCP's three-level execution handles Pipeline, Assembly Line, and Radial Burst patterns.
Full Conversion Map
See exactly what transfers from OpenClaw to .0n — manifests, tools, and MCP configs.
| Component | OpenClaw Field | .0n Target | Status |
|---|---|---|---|
| Agent Manifest | manifest.* | workflow.* | Full |
| MCP Servers | mcpServers{} | service connections | Full |
| Tool Definitions | tools[] | steps[].transform | Full |
| Claw Config | clawConfig.* | metadata.clawConfig | Full |
| Agent Name | manifest.name | workflow.name | Full |
| Runtime State | In-memory state | Not transferred | N/A |
How to Export from OpenClaw
Quick steps to extract your agent config and MCP setup.
Open OpenClaw Dashboard
Access your OpenClaw dashboard or project directory
Locate Your Agent
Find the agent or manifest you want to export
Export as JSON
Use the export function or click Export → JSON format
Include MCP Config
Make sure your mcpServers config is included in the export
Save the File
Download as .json or .claw file
Upload to Brain Transplant
Sign in to 0nMCP, go to Convert, and upload. We handle everything!
OpenClaw vs .0n Standard
| Feature | OpenClaw | .0n Standard |
|---|---|---|
| Tool Count | Varies by setup | 1,589 tools across 102 services |
| Portability | OpenClaw runtime only | Runs anywhere (any AI client) |
| Format | Claw / proprietary JSON | Open .0n Standard |
| Service Setup | Manual MCP bridges | 26 pre-built connectors |
| Execution Models | Sequential | Pipeline + Assembly Line + Radial Burst |
| Credential Management | Manual .env files | AES-256 Vault + Engine bundles |
| Community | Growing | npm + GitHub + Discord + Marketplace |
Frequently Asked Questions
Can I convert .claw files directly?
Yes! Brain Transplant supports both standard JSON exports and native .claw format files. Upload either format and we auto-detect and convert.
What happens to my MCP server configs?
MCP server configurations are mapped to 0nMCP service connections. If the service is one of our 26 built-in connectors, it maps automatically. Custom MCP servers are preserved as external service references.
Do I need to reconfigure my tools after conversion?
Most tools map directly to 0nMCP equivalents. If your OpenClaw setup used custom MCP servers, you may need to add those as external services. Built-in tools work immediately.
Is there a size limit for conversion?
Brain Transplant handles manifests up to 10MB. For larger multi-agent setups, you can split them into individual agent files and convert each one separately.
Can I convert back to OpenClaw format?
Yes — .0n files are human-readable and the conversion is non-destructive. You can always extract the original configuration data from the workflow metadata.
Upgrade Your Agents
Convert your OpenClaw agents to .0n and unlock 1,589 tools, 102 services, and the full 0nMCP ecosystem.