Public distribution

See exactly what MultiAiPanel ships publicly today, and what still needs an external publish step.

This page is the public truth ledger for MultiAiPanel distribution. It separates three ideas that are easy to mix up:

  • Public bundle: repo-owned assets you can copy today.
  • Official surface exists: the host ecosystem has a real public marketplace, registry, or plugin channel.
  • MultiAiPanel is officially listed there: an actual owner-controlled publish step already happened.

The supported install surface for MultiAiPanel itself remains the packaged GitHub Release zip. Browser-store submission materials are being kept ready, but store listing is still not the current public install surface.

The supported install path today is the packaged GitHub Release zip. Browser-store submission materials are being kept ready, but GitHub Releases remains the supported install surface today.

When you want the shortest packet for one host instead of the whole truth ledger, open the host packets page.

Docker / Glama truth: this repo now ships a Docker integration guide for the local MCP helper surface. That is a repo-owned container entry, not proof of a hosted compare service or an official Glama listing.

Official docs inspected for this page: 2026-04-07.

Current public distribution matrix

Host Official public surface What MultiAiPanel ships now Truthful public claim
Codex Official MCP configuration docs are verified.
No official MultiAiPanel marketplace or registry listing surface was verified from current official Codex docs. 		Repo-owned public bundle: the Codex starter files plus a bundle-ready archive directory, support matrix, public setup docs, placement hints, and smoke flow. Public bundle available now. No official marketplace listing claim.
Claude Code Official MCP configuration docs are verified.
No official MultiAiPanel marketplace or registry listing surface was verified from current official Claude Code MCP docs. 		Repo-owned public bundle: the Claude starter files plus a bundle-ready archive directory, support matrix, public setup docs, placement hints, and smoke flow. Public bundle available now. No official marketplace listing claim.
OpenCode Official config docs are verified, and official plugin docs expose a public plugin surface.
MultiAiPanel does not yet ship a published OpenCode plugin package. 		Repo-owned public-bundle-ready packet: the OpenCode config example, starter skill, plugin package scaffold, support matrix, public setup docs, placement hints, and compare-first proof loop. Public-bundle-ready packet available now. Official OpenCode plugin listing not shipped yet.
OpenClaw Official OpenClaw MCP, plugin, and bundle docs are verified through openclaw mcp set plus the bundle install docs.
The official docs inspected for this page do not prove a published Prompt Switchboard listing. 		Repo-owned public packet: the OpenClaw bundle archive, registry JSON, shell helper, compare-first skill content, support matrix, public setup docs, placement hints, and compare-first proof loop. Public-bundle-ready packet available now. No published OpenClaw listing claimed.

What the public bundle always includes

  • Repo-owned MCP config or registry snippets.
  • Starter skills or prompt instructions for the compare-first flow.
  • Placement hints so the last step is not hidden in prose.
  • The smallest useful proof loop: bridge_status, check_readiness, compare.
  • The preferred follow-through flow: analyze_compare, run_workflow, get_workflow_run, list_workflow_runs, resume_workflow.
  • README, FAQ, MCP docs, and the machine-readable support matrix kept in sync.

What this page does not overclaim

  • It does not say MultiAiPanel is already on an official marketplace unless a real listing happened.
  • It does not turn MultiAiPanel into a hosted relay, public API, or SDK.
  • It does not promote OpenCode or OpenClaw above the repo evidence bar.
  • It does not merge “official surface exists” with “we published there already.”

Release-ready host packets

MultiAiPanel can prepare downloadable per-host packet zips without cutting a new public release yet. That repo-owned packaging step is separate from any future marketplace or registry publication claim.

Run npm run release:host-kits to build release-ready public bundles under dist/public-bundles. The packet composition is driven by mcp/integration-kits/public-distribution-matrix.json.

The same public-bundle truth is also exposed through the MCP resource multi-ai-panel://builder/public-distribution.

Per-host bundle contents

Replace /absolute/path/to/MultiAiPanel with the real path to your own MultiAiPanel clone. The public bundle is meant to be directly copyable, not a prose-only packet.

Host Bundle assets Placement Proof loop
Codex codex-bundle/, Codex packet page, support matrix Paste the MCP block into config.toml. Start with bridge_status -> check_readiness -> compare.
Claude Code claude-code-bundle/, Claude Code packet page, support matrix Paste the MCP block into a Claude MCP config such as .mcp.json. Start with bridge_status -> check_readiness -> compare.
OpenCode opencode-plugin/, OpenCode packet page, support matrix Save it as project-root opencode.jsonc inside your MultiAiPanel clone. Use the same compare-first MCP flow, then expand into workflow follow-through.
OpenClaw OpenClaw packet page, openclaw-bundle/, Codex and Claude bundle archives, support matrix Register with openclaw mcp set or place the server entry under mcp.servers. Use the same compare-first MCP flow, then expand into workflow follow-through.

Official docs inspected for this page

Marketplace and registry proof ledger

Already true now

  • MultiAiPanel itself is publicly installable through GitHub Releases.
  • Codex, Claude Code, OpenCode, and OpenClaw each have repo-owned public bundles.
  • Host packets now exist for Codex, Claude Code, OpenCode, and OpenClaw.
  • The builder support matrix is public in docs, JSON, and the MCP resource surface.
  • The builder proof loop is public and machine-readable.

Still external-only

  • Browser-store submission and listing state.
  • Any future official Codex or Claude Code marketplace listing, if such a surface appears.
  • OpenCode plugin publication under an owner-controlled npm namespace.
  • Any future OpenClaw publication beyond the saved MCP registry flow already documented here.
  • Any future package-backed registry upgrade beyond the already-live websiteUrl-backed entry.

Exact external publish packets

Surface What is missing Who must act What to verify after
Browser store Dashboard access, listing submission, review-state proof Owner with store console permissions Rerun repo release and store readiness checks, then record listing status
OpenCode plugin listing Repo-owned plugin package plus npm namespace and publish permission Owner with package namespace control Verify package URL, docs link, and install flow
OpenClaw official listing or registry publication Any future package or listing beyond the saved MCP registry flow already documented here Owner with package or registry control Verify package URL, registry or listing URL, and install flow
Official MCP Registry No current blocker for the live entry; only later package-backed install upgrades or extra registry-proof work Owner only if a later package/auth upgrade is desired Verify the live registry URL, listed version, and install surface still point to the repo-backed MCP docs
.ai or domain alias DNS and registrar control Owner with domain access Rerun host frontdoor verification after redirect or alias setup

The official MCP Registry already returns a live MultiAiPanel MCP entry for the same local sidecar install surface. For the current repo truth, the strongest public distribution surface is the combination of GitHub Releases, the public docs front door, the repo-owned public bundles under mcp/integration-kits/, and that already-live registry entry.

OpenCode owner packet

  1. Run npm run release:host-kits and verify the OpenCode packet archive under dist/public-bundles/.
  2. Choose the owner-controlled npm package name and namespace for the OpenCode plugin package.
  3. Publish mcp/integration-kits/public-bundles/opencode-plugin/ to npm.
  4. Install it through the official OpenCode plugin flow and verify one compare-first smoke path.
  5. Only then update docs to claim MultiAiPanel is publicly published for OpenCode.

OpenClaw owner 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 URL or bundle URL and one compare-first smoke path after publish.
  5. Only then update docs to claim MultiAiPanel is publicly published for OpenClaw.

MCP Registry owner packet

  1. Keep the already-live Official MCP Registry entry aligned with the browser-first README and the MCP integration docs.
  2. Only plan extra registry work if you want a package-backed install upgrade beyond the current websiteUrl-backed entry.
  3. If that later upgrade matters, publish the package artifact first, then complete the exact auth and namespace steps for that artifact.
  4. Verify the live registry URL, listed version, and install surface before changing any broader marketplace claims.

Browser store owner packet

  1. Keep the repo-side packet green with npm run verify:store-readiness and the current release bundle assets.
  2. Open the browser-store dashboard, create or update the listing, and upload the release assets.
  3. Complete screenshots, metadata, and policy acknowledgements in the dashboard.
  4. Submit for review, then record the listing URL and review state.

What stays external-only

  • Namespace ownership, package publication, and registry listing creation.
  • Browser-store console access, listing submission, and review-state proof.
  • Official MCP Registry namespace authentication and listing publication.
  • .ai / DNS / registrar control.
  • GitHub social preview final manual confirmation after front-door visuals change.