OpenClaw packet

Use Prompt Switchboard with OpenClaw through bundle-friendly public packets without pretending the listing is already live.

OpenClaw already has an official CLI MCP path. Prompt Switchboard now ships a repo-owned OpenClaw public-bundle-ready packet and an exact install playbook without pretending an official Prompt Switchboard listing already exists.

Read official OpenClaw MCP docs Read official OpenClaw plugin docs Read official OpenClaw bundle docs

Current truth

Support class

  • Public-bundle-ready packet and generic MCP path today, not a verified repo-owned host lane yet
  • Official surface verified: OpenClaw CLI MCP docs, plugin docs, and bundle docs
  • Current repo claim: public packet shipped, no official Prompt Switchboard listing verified from the checked OpenClaw docs

Public packet contents

  • Packable OpenClaw bundle archive
  • OpenClaw MCP registry JSON and mcp.servers fragment
  • Compare-first smoke loop and follow-through map
  • Exact external packet if a later official listing surface appears

Install shape today

Today the strongest repo-owned OpenClaw packet is a public-bundle-ready packet plus MCP registry snippets. The checked official docs confirm the CLI MCP path. Any later listing claim still needs separate official proof. 

openclaw mcp set prompt_switchboard '{
  "command": "npm",
  "args": [
    "--prefix",
    "/absolute/path/to/multi-ai-sidepanel",
    "run",
    "mcp:server"
  ]
}'

Smallest useful smoke

  1. prompt_switchboard.bridge_status
  2. prompt_switchboard.check_readiness
  3. prompt_switchboard.compare

If you want a bundle-first install path, build the OpenClaw packet archive with npm run release:host-kits and install the generated archive from the OpenClaw bundle path after you verify the local MCP server works.

Public distribution truth

Owner-run publish packet

  1. Run npm run release:host-kits and verify the OpenClaw packet archive under dist/public-bundles/.
  2. Choose the official OpenClaw public surface you will really use: bundle install, plugin listing, or another official listing surface backed by OpenClaw docs.
  3. Publish the repo-owned OpenClaw packet and keep the MCP registry JSON, shell helper, and install docs aligned to that exact surface.
  4. Verify the listing or bundle URL, the install flow, and one compare-first smoke run after publish.
  5. Only after those proofs exist should you update public docs to claim Prompt Switchboard is publicly published for OpenClaw.