Overview
ClawMagic Marketplace plugins ship as .zip packages. These packages can be installed into OpenClaw (theclaw) using either a manual download-and-extract flow or the automated agent marketplace API.
Both methods result in the plugin being placed in the OpenClaw extensions directory and enabled in your configuration.
| Method | Best For | Auth Required |
|---|---|---|
| Manual ZIP install | Quick setup, one-off installs, testing | Marketplace account |
| Agent automation | Repeatable installs, CI/CD, agent workflows | API key (cmk_*) |
Prerequisites
- OpenClaw (theclaw) installed and running — the CLI must be available as
openclawin your terminal. - Extensions directory exists at
~/.openclaw/extensions/(created automatically on first run, or set viaOPENCLAW_STATE_DIR). - A ClawMagic Marketplace account for purchasing or claiming free plugins.
Method 1: Manual ZIP Install
Download a plugin .zip from the ClawMagic Marketplace website and install it into OpenClaw using the CLI.
Step 1: Download the plugin
- Go to the ClawMagic Marketplace and find the plugin you want.
- Click the plugin to open its detail page.
- Click Download (free plugins) or complete checkout (paid plugins). The
.zipfile will download to your computer.
Step 2: Install with the OpenClaw CLI
Use the openclaw plugins install command, passing the path to the downloaded ZIP:
# Install from downloaded ZIP openclaw plugins install ~/Downloads/my-plugin.zip # Verify it appears in the plugin list openclaw plugins list
The CLI extracts the ZIP, validates the plugin manifest, scans for security issues, and places the plugin in ~/.openclaw/extensions/<plugin-id>/.
Step 3: Enable the plugin
# Enable the plugin in your config openclaw plugins enable <plugin-id> # Confirm it's enabled openclaw plugins list
This sets config.plugins.entries.<id>.enabled: true in ~/.openclaw/config.json. The plugin loads on the next OpenClaw startup.
Alternative: Manual extraction (without CLI)
If you prefer to extract manually instead of using the CLI command:
# 1. Create the plugin directory mkdir -p ~/.openclaw/extensions/my-plugin # 2. Extract the ZIP into it unzip ~/Downloads/my-plugin.zip -d ~/.openclaw/extensions/my-plugin # 3. Verify the manifest exists cat ~/.openclaw/extensions/my-plugin/openclaw.plugin.json # 4. Enable in config openclaw plugins enable my-plugin
The directory name under extensions/ should match the plugin id in the manifest. If the ZIP contains a claw.plugin.json (ClawMagic format) but no openclaw.plugin.json, the plugin may need the compatibility manifest added manually.
Plugin Package Structure
ClawMagic Marketplace plugins ship as ZIP files. Here is what you will find inside:
my-plugin.zip
├── claw.plugin.json # ClawMagic marketplace manifest
├── actionspec.json # Action specification bundle
├── skill.json # Skill hints for agent routing
├── README.md # Plugin documentation
├── plugin/ # Bundled runtime code
│ ├── index.js # Entry point
│ └── ...
├── openclaw.plugin.json # OpenClaw compatibility manifest (if included)
└── skills/
└── my-plugin/
└── SKILL.md # Operational guidanceOpenClaw discovers plugins by looking for openclaw.plugin.json in the extensions directory. If the marketplace ZIP includes this file, the plugin is ready to use. If it only has claw.plugin.json, see the compatibility note below.
ClawMagic vs OpenClaw Manifests
ClawMagic plugins use claw.plugin.json as their manifest. OpenClaw uses openclaw.plugin.json. Many marketplace plugins include both for cross-system compatibility.
| File | Used By | Key Fields |
|---|---|---|
claw.plugin.json | ClawMagic | id, name, version, type, entry, permissions, install, support |
openclaw.plugin.json | OpenClaw (theclaw) | id, channels, configSchema, name, description, version, kind |
If a marketplace plugin does not include openclaw.plugin.json, you can create a minimal one:
{
"id": "my-plugin",
"channels": [],
"configSchema": {
"type": "object",
"additionalProperties": false,
"properties": {}
}
}Place this file at the root of the plugin directory alongside claw.plugin.json.
Managing Installed Plugins
# List all installed plugins openclaw plugins list # Enable a plugin openclaw plugins enable <plugin-id> # Disable a plugin (keeps files, stops loading) openclaw plugins disable <plugin-id> # Uninstall a plugin (removes files) openclaw plugins uninstall <plugin-id>
Plugin state is stored in ~/.openclaw/config.json under plugins.entries (enabled/disabled) and plugins.installs (install metadata including source, version, and path).
Method 2: Automated Agent Install
For repeatable installs and agent-driven workflows, use the ClawMagic Marketplace API to browse, purchase, download, and install plugins programmatically. This is the same flow documented in the Agent Marketplace docs.
Step 1: Get an API key
Create a scoped API key from an authenticated session:
POST /v1/apikeys
Authorization: Bearer mpk_live_...
Content-Type: application/json
{
"name": "openclaw-agent-key",
"scopes": ["deliveries:read", "deliveries:write"]
}
# Response (save the key — shown once):
{
"id": "key_abc123",
"token": "cmk_live_...",
"scopes": ["deliveries:read", "deliveries:write"]
}Step 2: Browse and purchase
# Browse plugins (public, no auth required)
GET /v1/plugins?q=seo&limit=10
# Purchase / claim a free plugin
POST /v1/checkout/create
Authorization: Bearer cmk_live_...
Content-Type: application/json
{
"pluginId": "plugin_id_here",
"quantity": 1
}
# Free plugins finalize immediately:
{
"entitlementId": "ent_abc123",
"providerStatus": "FREE_CLAIM",
"downloadToken": "dtk_..."
}Step 3: Download the package
# Request a signed download URL
POST /v1/agent/deliveries/request
Authorization: Bearer cmk_live_...
Content-Type: application/json
{
"entitlementId": "ent_abc123"
}
# Response:
{
"downloadUrl": "https://storage.../my-plugin.zip?sig=...",
"sha256": "a1b2c3d4...",
"fileName": "my-plugin-1.0.0.zip"
}
# Download and verify
curl -o my-plugin.zip "$downloadUrl"
sha256sum my-plugin.zip # must match response sha256Step 4: Install into OpenClaw
# Install using the CLI openclaw plugins install ./my-plugin.zip # Enable the plugin openclaw plugins enable my-plugin # Verify openclaw plugins list
Step 5: Report install status
Report the install result back to the marketplace so install counts and rankings stay accurate:
POST /v1/agent/install-report
Authorization: Bearer cmk_live_...
Content-Type: application/json
{
"entitlementId": "ent_abc123",
"status": "SUCCESS",
"pluginVersion": "1.0.0",
"runtime": "openclaw"
}Use "status": "FAILED" with an optional error field if the install did not succeed.
Troubleshooting
| Issue | Solution |
|---|---|
Plugin not showing in openclaw plugins list | Verify the directory exists at ~/.openclaw/extensions/<plugin-id>/ and contains openclaw.plugin.json. |
| Plugin shows but won't load | Run openclaw plugins enable <plugin-id> and restart OpenClaw. Check ~/.openclaw/config.json for the entry. |
No openclaw.plugin.json in the ZIP | Create a minimal manifest (see the compatibility section above) and place it at the plugin root. |
| Permission denied errors | OpenClaw performs ownership checks on Unix systems. Ensure the extensions directory and plugin files are owned by your user, not root. |
| SHA-256 mismatch on download | Re-download the ZIP. If the hash still doesn't match, the download may have been corrupted in transit. Request a new delivery URL. |
OpenClaw Plugins & ClawMagic Plugins
ClawMagic Marketplace plugins can be installed into either ClawMagic or OpenClaw. Pick the guide that matches your runtime:
- ClawMagic Plugin Install — Install plugins into a ClawMagic server instance.
- OpenClaw Plugin Install — You are here. Install the same marketplace plugins into OpenClaw (theclaw).
Related Docs
- Agent Marketplace — Full API reference for automated browse, purchase, download, and install.
- Plugin Packaging — How marketplace plugins are structured and validated.
- Plugin Development — Build your own plugins with ActionSpec, skill hints, and manifests.
- Dual Install — Running ClawMagic and OpenClaw side by side.
- Browse Marketplace — Find plugins to install.