multicorn-shield 0.2.1 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +22 -0
- package/dist/multicorn-proxy.js +385 -470
- package/dist/multicorn-shield.js +118 -0
- package/dist/openclaw-hook/handler.js +2 -2
- package/dist/openclaw-plugin/multicorn-shield.js +2 -2
- package/dist/proxy.cjs +457 -0
- package/dist/proxy.d.cts +235 -0
- package/dist/proxy.d.ts +235 -0
- package/dist/proxy.js +438 -0
- package/dist/shield-extension.js +23858 -0
- package/package.json +25 -6
package/README.md
CHANGED
|
@@ -54,6 +54,28 @@ That's it. Every tool call now goes through Shield's permission layer, and activ
|
|
|
54
54
|
|
|
55
55
|
See the [full MCP proxy guide](https://multicorn.ai/docs/mcp-proxy) for Claude Code, OpenClaw, and generic MCP client examples.
|
|
56
56
|
|
|
57
|
+
### Claude Desktop Extension (.mcpb)
|
|
58
|
+
|
|
59
|
+
Install Shield without the terminal: download the `.mcpb` bundle (or use **Install** from the Shield product page), open it in Claude Desktop, and enter your API key when prompted. The extension reads your existing MCP servers from `claude_desktop_config.json`, runs them as child processes, merges their tools, and checks every `tools/call` with the Shield API. Activity still shows up in your [Multicorn dashboard](https://app.multicorn.ai).
|
|
60
|
+
|
|
61
|
+
**Disable or uninstall recovery:** On each start the extension saves a copy of your `mcpServers` block to `~/.multicorn/extension-backup.json` with restricted file permissions (owner read/write only). If you turn the extension off and need your original Claude Desktop MCP entries back, run:
|
|
62
|
+
|
|
63
|
+
```bash
|
|
64
|
+
npx multicorn-shield restore
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
Then restart Claude Desktop. That overwrites `mcpServers` in your config with the last backup.
|
|
68
|
+
|
|
69
|
+
**Duplicate tool names:** If two MCP servers expose the same tool name, the first server in your config file keeps the name. The duplicate is skipped and a warning is written to the extension logs (stderr). Rename tools on the server side if you need both.
|
|
70
|
+
|
|
71
|
+
Build the bundle locally (requires a full `pnpm build` first):
|
|
72
|
+
|
|
73
|
+
```bash
|
|
74
|
+
pnpm run pack:extension
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
This runs `mcpb validate` and writes `dist/multicorn-shield.mcpb`.
|
|
78
|
+
|
|
57
79
|
### Option 2: OpenClaw Plugin (native integration)
|
|
58
80
|
|
|
59
81
|
If you're running [OpenClaw](https://openclaw.ai), Shield integrates directly as a plugin. No proxy layer, no code changes. The plugin intercepts every tool call at the infrastructure level before it executes.
|