What we've learned shipping Meridian — an MCP server with real auth, Stripe billing, RAG via Vectorize, and SSE streaming on Cloudflare's free tier. Plus side notes on photonic / quantum retrieval research.
Grok's custom MCP connectors take a server URL + an OAuth dance. We just wired Meridian's orbital skill router into it. The architecture, the OAuth values to paste, and the design choice that lets Grok users authorize with one click — no GitHub PAT, no jargon, no setup wizard.
We just shipped meridian-skills-mcp 2.0.0 to both registries from a single tag push. The honest tradeoff: anonymous install still requires npm, but for everything else GitHub Packages has earned its slot — auth shared with your code, automatic provenance, free private packages, same registry as your Docker images. The full release workflow + the npm pkg set name rename trick that lets one tarball ship under two names.
Most MCP tutorials show npx create-mcp and a Hello-world tool. Real servers in production need auth, per-key quotas, billing, and an upgrade path. Here's the architecture we use for ask-meridian.uk — entirely on Cloudflare's free tier — and the specific gotchas you'll hit.
Most RAG systems either retrieve from a static corpus or end-to-end LLM-rank. Meridian does neither. Llama-3.3-70B authors fresh skills per task; a deterministic JS classifier assigns each one a celestial class (planet/moon/trojan/asteroid/comet/irregular) based on physics-style features. Why the metaphor, why the deterministic step, and where it goes next.
Workers AI for embeddings (free tier), Vectorize for semantic search (free tier), AI Gateway for caching + observability (free). The whole stack costs $0 until you cross 100k requests/month. Here's the wiring we use for meridian's RAG layer.