Outreach: MCP registry submission + Glama claim + awesome-list PR follow-ups
Status: technically fire-ready; the remaining steps are founder browser actions + maintainer merges.
MCP registry (FIRE-READY, needs founder browser ~2 min)
- Published
loki-mode@7.34.x has mcpName: io.github.asklokesh/loki-mode (the registry ownership marker). VERIFIED.
- Published-package MCP handshake verified: fresh install + project venv + full
initialize -> notifications/initialized -> tools/list returns 34 tools over stdio.
- Server.json entry is staged (90-char description to pass the 100-char server-side cap). Full runbook:
internal/outreach-staged/mcp-registry-submission.md (refreshed to 7.34).
- BLOCKER: the registry publish needs an interactive device-code auth (GitHub OAuth) the founder runs in a browser; the poller/flow is restartable.
Glama (badge GREEN, needs founder web claim)
- Glama's clean-room introspection passes (34 tools from the published Docker image; the v7.31.0 Dockerfile ships mcp/requirements.txt). Section 6b walkthrough in
internal/outreach-staged/mcp-registry-submission.md.
- BLOCKER: interactive web repo-claim (founder), then post the gated-badge comment on the Glama tracking issue.
Awesome-list PRs (await maintainer merge, monitor)
Open PRs (as of 2026-06-11):
Cold-launch UX note (founder decision, non-blocking)
loki mcp over piped stdio is non-interactive and exits 2 without the MCP SDK present (never auto-installs). A registry consumer with the SDK (or who runs the documented bootstrap) gets the 34-tool handshake. Founder may decide whether to soften this UX later.
Outreach: MCP registry submission + Glama claim + awesome-list PR follow-ups
Status: technically fire-ready; the remaining steps are founder browser actions + maintainer merges.
MCP registry (FIRE-READY, needs founder browser ~2 min)
loki-mode@7.34.xhasmcpName: io.github.asklokesh/loki-mode(the registry ownership marker). VERIFIED.initialize -> notifications/initialized -> tools/listreturns 34 tools over stdio.internal/outreach-staged/mcp-registry-submission.md(refreshed to 7.34).Glama (badge GREEN, needs founder web claim)
internal/outreach-staged/mcp-registry-submission.md.Awesome-list PRs (await maintainer merge, monitor)
Open PRs (as of 2026-06-11):
One already merged earlier (state-machine doc / eltociear). Action: monitor, nudge if stale, respond to maintainer review comments.
Cold-launch UX note (founder decision, non-blocking)
loki mcpover piped stdio is non-interactive and exits 2 without the MCP SDK present (never auto-installs). A registry consumer with the SDK (or who runs the documented bootstrap) gets the 34-tool handshake. Founder may decide whether to soften this UX later.