Distribution & publishing playbook (multi-channel MCP/plugin listing)

[ucsandman]

Distribution & publishing playbook (multi-channel MCP/plugin listing)

Source: .handoff-notes-integration-audit-2026-06-10.md (distribution research, web-verified 2026-06-10). Corrected 2026-06-11: mcp-publisher npm warning + publish status.

Decision rule: DON'T pick one — channels are complementary; publish in dependency order. The phases below are ordered by dependency and must be executed in sequence.

Phase 1 (~2h, unblocks the rest)

• Official MCP Registry — "mcpName": "io.github.ucsandman/dashclaw" is already in the mcp-server package.json. ⚠️ Do NOT npm i -g mcp-publisher — that npm package name is squatted; the official mcp-publisher is a Go binary (already installed locally per the 2026-06-10 audit). Run mcp-publisher init / login github / publish with the Go binary. This auto-feeds PulseMCP.
• Glama — submit the repo URL. This is a HARD prerequisite for the punkpeye list in Phase 2.
• GitHub topics — add: mcp, model-context-protocol, claude-code, ai-governance, agent-governance, mcp-server.
• npm / PyPI keywords — same set as the GitHub topics.

Phase 2

• punkpeye/awesome-mcp-servers PR (88k★) — needs Glama (Phase 1) first.
• PulseMCP — direct submit.
• mcp.so — submission form.
• Smithery — smithery mcp publish.
• mcp.directory — /submit + /submit-skill.
• SkillsMP — auto-indexes SKILL.md (needs 2+ repo stars).

Phase 3 (Claude Code)

• hesreallyhim/awesome-claude-code PR (46k★ — the most important single list).
• rohitg00/awesome-claude-code-toolkit PR.
• anthropics community marketplace PR (claude-plugins-community).
• Official Anthropic plugin directory — form at clau.de/plugin-directory-submission (low odds, free to try).
• claudepluginhub.com / tonsofskills.com — URL submits.
• Skills ship BOTH inside the plugin AND as a standalone GitHub SKILL.md (free).

Phase 4 (launch day, coordinate)

• Reddit: r/ClaudeAI (916k) + r/mcp + r/LocalLLaMA.
• Show HN — hand-write the README (HN flags AI-sounding copy).
• dev.to tutorial.
• Newsletters 1 week ahead: TLDR AI, Ben's Bites, Latent Space.
• Product Hunt — 2–3 weeks out.

Phase 5

• ClawHub for OpenClaw plugin — OpenClaw compat metadata already in package.json; requires CI + signing + VirusTotal (1–2 weeks).
• Hermes — file an issue on 0xNyk/awesome-hermes-agent + submit skillsdock.io (covers OpenClaw + Hermes + Claude Code in one).

Phase 6 (separate milestone)

• Anthropic Claude.ai Connectors Directory — needs the REMOTE MCP path: /api/mcp + OAuth already EXISTS in the repo. The directory requires: an HTTPS streamable endpoint, OAuth (callback https://claude.ai/api/mcp/auth_callback), readOnlyHint/destructiveHint annotations on every tool, a privacy policy, and a test account. Submit via clau.de/mcp-directory-submission (needs a Team/Enterprise org). Highest reach, multi-week review.

Publish status (verified against the registries 2026-06-11)

• @dashclaw/mcp-server — 2.0.0 published to npm (the earlier "repo 1.0.3 vs npm 1.0.2" note is obsolete). Nothing owed.
• @dashclaw/cli — 0.3.2 published. Nothing owed.

[ucsandman]

Phase 1–3 execution status (2026-06-11)

Channel	Status	Detail
Official MCP Registry	✅ LIVE	io.github.ucsandman/dashclaw 2.0.0, isLatest: true (was already published; verified)
PulseMCP	✅ LIVE	pulsemcp.com/servers/dashclaw — auto-fed from the official registry
GitHub topics	✅ DONE	already set (incl. mcp, mcp-server, claude-code, ai-governance)
npm / PyPI keywords	✅ DONE	already set on @dashclaw/mcp-server
mcp.directory	🟡 SUBMITTED	form accepted ("publish within 24 hours"); email notification to wes@
mcp.so	🟡 SUBMITTED	comment on the canonical submission thread chatmcp/mcp-directory issue #1 as ucsandman
rohitg00/awesome-claude-code-toolkit	🟡 PR OPEN	rohitg00/awesome-claude-code-toolkit#528
SkillsMP	🟡 AUTO	indexes SKILL.md repos with 2+ stars — should pick up on its own crawl
Glama	🔴 WES-MANUAL	signup wall + captcha blocks automation. Steps: glama.ai/mcp/servers → "Add Server" → sign up (OAuth) → submit repo https://github.com/ucsandman/DashClaw, npm @dashclaw/mcp-server, PyPI dashclaw, description: "Self-hosted governance control plane for AI agents: guard, approve, and record every risky action via MCP server, Claude Code hooks, or Node/Python SDKs." Gates the punkpeye PR.
punkpeye/awesome-mcp-servers	⏸ GATED	requires the Glama listing first; PR ready to open the moment Glama lists us
hesreallyhim/awesome-claude-code	🔴 WES-MANUAL	PRs/CLI explicitly rejected; submit via their web issue form: https://github.com/hesreallyhim/awesome-claude-code/issues/new?template=recommend-resource.yml
anthropics community marketplace	🔴 WES-MANUAL	repo is a read-only mirror; submit via https://clau.de/plugin-directory-submission (manifest: plugins/dashclaw/.claude-plugin/plugin.json, v2.15.0)
mcp.directory /submit-skill	⬜ TODO	separate skill submission for the governance SKILL.md — low effort, can ride a future pass
Smithery	⏸ DEFERRED	requires publishing a hosted streamable-HTTP endpoint (the /api/mcp + OAuth path) — same prerequisite family as Phase 6; decide together with the Connectors Directory work

Net: every Phase 1–3 channel is live, submitted, PR'd, or reduced to a 4-item manual queue (Glama → unlocks punkpeye, hesreallyhim form, clau.de form). Phase 4 (launch one-shot) intentionally deferred until the dogfood loop work (#147 → close-the-loop spec) is finished.

[ucsandman]

The two code-actionable Phase-1 items are already in place on main:

• GitHub topics — the repo already carries mcp, model-context-protocol, claude-code, ai-governance, agent-governance, mcp-server (and more).
• npm keywords — mcp-server/package.json already has the exact set.

Everything else here (Official MCP Registry publish via the Go mcp-publisher binary, Glama / PulseMCP / mcp.so / Smithery submissions, the awesome-list PRs, Reddit / Show HN / Product Hunt, ClawHub / Hermes, the Anthropic Connectors directory) is external submission work requiring credentials, third-party accounts, and manual PRs — none of it is committable from this repo. Leaving open as the human-driven distribution tracker; no code change is owed.

[ucsandman]

Maintainer state audit (2026-07-28) — what's verifiably done vs. what remains, so this playbook reflects reality:

Done (verified today):

• GitHub topics: all six from Phase 1 are live on the repo (mcp, model-context-protocol, claude-code, ai-governance, agent-governance, mcp-server), plus a wider set.
• mcpName: io.github.ucsandman/dashclaw is in mcp-server/package.json.
• Keywords: present on every published manifest — sdk/package.json, mcp-server/package.json, sdk-python/pyproject.toml (root package.json is the unpublished app; keywords there don't reach any registry).
• Glama: submitted and rated (A/A/A across categories, per the roadmap-v6 record) — the Phase 2 hard prerequisite is cleared.
• punkpeye/awesome-mcp-servers: PR #9313 opened, awaiting upstream human merge.

Remaining — all credential-gated or outward-facing publishing, which stays human per MAINTAINER.md invariant 4:

• Official MCP Registry publish via the Go mcp-publisher binary (login + publish). Reminder from the original audit stands: the npm package of that name is squatted — do not npm i -g mcp-publisher.
• Phase 2 direct submits (PulseMCP, mcp.so, Smithery, mcp.directory, SkillsMP).
• Phase 3 Claude Code list PRs + Anthropic directory form.
• Phase 4 launch-day posts (Reddit / Show HN / dev.to / newsletters).

Everything the maintainer can do from the repo for this playbook is done; the rest is a human checklist in dependency order, starting with the ~15-minute MCP Registry publish.

[ucsandman]

Status re-verified live 2026-07-28 (the issue body's 2026-06-11 numbers are stale):

Phase 1 — mostly done:

• GitHub topics: ✅ all six recommended topics are live (plus 12 more).
• Glama: ✅ submitted and rated A/A/A.
• Official MCP Registry: ⚠️ listed but two releases stale — registry serves 1.0.3, npm serves 3.0.2, repo is at 3.1.0. One credential-gated npm run release:mcp publishes 3.1.0 to npm + registry in a single idempotent run (scripts/release-mcp-server.mjs handles both; server.json synced to 3.1.0 on main today). This is the one Phase-1 step still owed, and it's human-gated.
• npm keywords: ✅ @dashclaw/mcp-server carries the full mcp/claude-code/governance set; dashclaw SDK carries the governance set. PyPI keyword changes would require a republish — not worth one on their own; fold into the next SDK release.

Phase 2:

• punkpeye/awesome-mcp-servers PR #9313: still open, awaiting upstream maintainer — nothing to do on our side.

Publish status corrections: @dashclaw/mcp-server npm is now 3.0.2 (issue says 2.0.0), @dashclaw/cli is 0.9.1 (issue says 0.3.2), SDKs are at 5.6.2 on npm + PyPI as of today.

Phases 3–6 remain human-gated (list PRs under Wes's name, account-bound form submits, Show HN copy). Keeping this open as the playbook of record.

[ucsandman]

Phase 1 fully discharged: Wes ran npm run release:mcp — verified live: npm @dashclaw/mcp-server@3.1.0 (dist-tag latest) and MCP registry io.github.ucsandman/dashclaw 3.1.0 flagged isLatest: true (all 7 versions listed).

Correction to my previous comment: "registry serves 1.0.3" was a misread on my part — the registry's search endpoint returns all version records oldest-first and I quoted the first element. The registry's actual latest before today was 3.0.0 (one release behind npm's 3.0.2, not two-and-a-half years of drift). The gap is closed either way.

Remaining phases (2–6) are all human-gated. Nothing owed on the automated side.