@npcink/magick-ai-adapter-cli
v0.1.0
Published
Local signed key-pair CLI for Magick AI Adapter.
Readme
Magick AI Adapter CLI
Local signed key-pair CLI for connecting OpenClaw-style clients to Magick AI Adapter without sending a WordPress Application Password to chat, prompts, tool commands, logs, proposal payloads, or copied handoff text.
Usage
Connect from the user's local machine:
npx -y @npcink/magick-ai-adapter-cli connect --site=https://example.com --profile=exampleCheck the local profile and signed Adapter health:
npx -y @npcink/magick-ai-adapter-cli status --profile=exampleCall Adapter through the signed local wrapper:
npx -y @npcink/magick-ai-adapter-cli request --profile=example GET /health
npx -y @npcink/magick-ai-adapter-cli request --profile=example GET /capabilitiesFor local WordPress development sites with self-signed .local HTTPS, add
--insecure-local-tls.
Before the package is published to npm, test this repo-local package with:
npx --yes --package /path/to/magick-ai-adapter/packages/adapter-cli magick-adapter status --profile=exampleSecurity Boundary
The CLI generates the private key locally and stores it under
~/.magick-ai-adapter/keypair-profiles/. Magick AI Adapter stores only the
approved public key and verifies signed REST requests. Do not ask an AI client
to read, print, summarize, or copy the profile JSON file.
