Ship the Mukoko Events MCP: deploy it live, publish to registry, land dual-domain + search, then split MCP/admin into their own repos

[bryanfawcett]

Work spec for a follow-up session. The MCP is fully built in code but not serving in production, and several adjacent pieces are staged in open PRs. This issue is the ordered checklist to finish it.

Background — what's already merged to main

This session merged, verified green (lint + 716 app tests + 58 admin tests + builds):

• feat(brand): "by Mukoko Events" descriptor under the Nhimbe wordmark #94 — "by Mukoko Events" wordmark lockup
• feat(mcp): events.mukoko.com-only routing + tool titles/annotations + registry declaration #95 — MCP single-domain routing (events.mukoko.com/mcp only) + tool title/annotations + worker/server.json registry declaration
• feat(skills): Agent Skills for the Mukoko Events MCP (discovery + hosting) #96 — two consumer skills (skills/mukoko-events-discovery, skills/mukoko-events-hosting)
• feat(search): ⌘K command palette (nyuchi-command-palette) wired into the header #97 — ⌘K command palette wired into the header
• feat(mcp): structured output on every tool + self-contained workspace #98 — MCP structured output (outputSchema + structuredContent on all 5 tools) + worker/ made a self-contained, extraction-ready workspace
• feat(plugin): Mukoko Events Claude plugin + marketplace + ChatGPT connector #99 — Claude Code plugin (plugins/mukoko-events/) + repo marketplace (.claude-plugin/marketplace.json) + ChatGPT connector (connectors/chatgpt/)

The MCP server code (worker/) is complete: dual-era protocol (legacy + 2026-07-28 beta), titles/annotations, input and output schemas, structured content, server.json. claude plugin validate passes on both manifests.

---

1. 🔴 Deploy the Worker — make events.mukoko.com/mcp actually live (highest priority)

Current state: POST https://events.mukoko.com/mcp returns the Next.js app HTML with an x-vercel-id header — i.e. the request falls through to Vercel because the Cloudflare Worker route is not intercepting /mcp/*. nhimbe.com/mcp also (correctly) does not serve the MCP.

Do:

• Ensure the events.mukoko.com DNS record on the mukoko.com Cloudflare zone is Proxied (orange cloud) in front of Vercel (see worker/README.md → "DNS / routing").
• Deploy the Worker: cd worker && npx wrangler deploy --env production (needs Cloudflare auth / CLOUDFLARE_API_TOKEN). wrangler.toml already registers only the events.mukoko.com/mcp + /mcp/* routes.
• Verify live:

  curl https://events.mukoko.com/mcp -X POST -H 'content-type: application/json' \
    -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
  

  Expect the 5 tools with title, annotations, inputSchema, outputSchema — not app HTML / an x-vercel-id header.
• Confirm nhimbe.com/mcp still does not serve the MCP (hard rule: single MCP domain).

2. Publish to the MCP registry

• worker/server.json (name com.mukoko/nhimbe-events) is ready. Publish per worker/README.md → "MCP registry": verify the com.mukoko DNS namespace via a TXT record on mukoko.com, mcp-publisher login dns --domain mukoko.com, then cd worker && mcp-publisher publish.
• Keep version in server.json and worker/package.json in lockstep on each release.

3. Land the two open PRs (staged, off an older main — rebase first)

• feat(seo): dual-domain support — one canonical origin (events.mukoko.com) #92 — dual-domain (events.mukoko.com + nhimbe.com, canonical = events.mukoko.com). Rebase onto main, merge. Then the ops follow-ups (not code): add both domains to the Vercel project; register both /callback URLs in WorkOS; set NEXT_PUBLIC_SITE_URL=https://events.mukoko.com (prod + preview).
• feat(search): hybrid vector⊕full-text retrieval (RRF) with graceful fallback #93 — hybrid search (vector ⊕ full-text RRF with graceful fallback). Rebase onto main, merge. Then the platform DB asks in docs/search-platform-requests.md: create event_vector_index on events.eventEmbeddings (768-dim cosine + city/category filters) and events_text_index (Atlas Search) on events.events; later upgrade the cluster to 8.1 for native $rankFusion + evaluate automated (Voyage) embeddings.

4. Split MCP and admin into their own repos

Both are extraction-ready (self-contained, share no code with the app beyond HTTP APIs).

• nyuchi/mukoko-events-mcp ← move worker/ (+ the plugins/, .claude-plugin/marketplace.json, connectors/, and top-level skills/ distribution surfaces, or decide which travel with it). Update repository/source fields in worker/package.json, worker/server.json, plugin.json, marketplace.json. Remove the worker jobs from this repo's ci.yml and add a deploy workflow in the new repo.
• nyuchi/mukoko-events-admin ← move admin/. It's currently a hoisted npm workspace member that imports the root src/* via @/* tsconfig paths — extraction needs those shared modules vendored or published, so plan that dependency break before moving. Give it its own Vercel project wiring (already documented in admin/README.md).

5. Follow-ups / smaller items

• Palette → autocomplete: once feat(search): hybrid vector⊕full-text retrieval (RRF) with graceful fallback #93 merges, switch the header ⌘K live search from searchEventsAction to the lighter autocompleteEventsAction for snappier per-keystroke results (src/components/layout/header.tsx).
• SSR-first sweep: these pages are "use client" and could be server-rendered for the SSR-first goal — evaluate/convert where they don't need client state: /search, /my-events, /calendar, /profile. (Core browse surfaces — home, /discover, /events, /events/[id] — are already SSR.)
• MongoDB "repeated things": a duplicate-data concern was raised but not pinpointed. Swept collections (campfire.conversations, events.events, identity.persons, entity.entities) were clean; needs the specific collection/screen to investigate.

Guardrails

• Single MCP domain: the MCP is served only at events.mukoko.com/mcp, never nhimbe.com/mcp. The app stays dual-domain; the MCP does not.
• Worker owns no data: every tool calls the app's public HTTP API; the app is the single trust boundary (WorkOS bearer verified in src/lib/auth/workos-token.ts).
• Repo house style: claude/<topic> branches, draft PRs, squash-merge.

🤖 Generated with Claude Code

[linear]

NYU-41

[bryanfawcett]

Progress: repo split shipped (part 4), follow-ups filed (part 5)

An agent fleet worked this issue across all four repos. Four draft PRs, all green on GitHub Actions CI:

PR	What	CI
mukoko-events-mcp#1	worker/ + plugins/marketplace/connectors/skills extracted to repo root; repo-location URLs rewritten; version lockstep 2.0.0-beta.1; CI + gated deploy workflows	Tests + Type Check ✅ (33 tests)
mukoko-events-admin#1	admin/ extracted, self-contained via a vendored shared/ tree (@/* → ./shared/*); own CI workflow; lockfile synced for npm ci	Lint & Build + Tests ✅ (58 tests)
nhimbe#101	Removed worker/ + admin/ + distribution surfaces; pruned ci.yml/workspaces; rewrote CLAUDE.md/README/AGENTS.md; part-5 report in docs/issue-100-followups.md	All checks ✅ (716 tests)
nyuchi-docs#34	New Integrations page documenting the Mukoko Events MCP (endpoint, 5 tools, connect paths) + sidebar wiring	build ✅

Part 5 follow-ups (documented in nhimbe/docs/issue-100-followups.md)

• Palette → autocomplete: blocked on feat(search): hybrid vector⊕full-text retrieval (RRF) with graceful fallback #93 (autocompleteEventsAction doesn't exist yet); exact two-line change recorded for when feat(search): hybrid vector⊕full-text retrieval (RRF) with graceful fallback #93 lands.
• SSR-first sweep: /my-events = best SSR candidate; /calendar = partial; /search = pairs with feat(search): hybrid vector⊕full-text retrieval (RRF) with graceful fallback #93; /profile = keep client. No conversions made (out of scope for the split).
• MongoDB duplicates: swept-clean collections captured; open item still needs a specific collection/screen to pinpoint.

Not done — ops actions requiring credentials (parts 1, 2, 3-ops)

These need Cloudflare / WorkOS / Vercel / DNS access and can't be done from a code session:

1. Deploy the Worker (part 1): orange-cloud events.mukoko.com DNS + wrangler deploy --env production. Now runs from the new mukoko-events-mcp repo.
2. Publish to the MCP registry (part 2): com.mukoko DNS TXT verify → mcp-publisher publish from mukoko-events-mcp.
3. PRs feat(seo): dual-domain support — one canonical origin (events.mukoko.com) #92 (dual-domain) / feat(search): hybrid vector⊕full-text retrieval (RRF) with graceful fallback #93 (hybrid search): still need rebase + merge, plus their WorkOS/Vercel/Atlas-index ops follow-ups.
4. Vercel: decommission the old nhimbe-admin project (root dir admin/, now empty → red on chore(#100): remove extracted MCP worker + admin app, rewire, add part-5 follow-ups #101) and stand up a new project pointed at mukoko-events-admin. Same for adding a Vercel project + Workers Builds trigger for mukoko-events-mcp.

---

Generated by Claude Code