MCP Hub
BlogAbout

BUILD LOG

I wanted a fast, trustworthy MCP directory. Codex sat in the editor with me, wrote the boring bits, and kept me moving. Here's the short version.

How I worked with Codex

I mapped the pages first—home, MCP detail, auth, about—and told Codex the flow I wanted. It drafted the routes, metadata, and base components while I pushed the tone and UX. We bounced on styling together: Codex suggested Tailwind stacks, I nudged spacing, focus states, and copy. Lint and typecheck ran in the background so every change stayed small.

Tips if you want to try this

If you try this, tell the AI the destination instead of the next line of code. Keep the stack boring so it can handle the glue. Let it draft the copy too—consistency matters as much as features—and keep lint and typecheck humming so nothing drifts far from green.

Tech Stack

Frontend

  • Next.js 16 (App Router), React 19, TypeScript strict
  • Tailwind for layout/spacing; Radix + Lucide for UI and icons
  • Framer Motion + Embla for motion and carousels

Data & Infra

  • Supabase for auth, database, and storage
  • nuqs for typed search params; OpenPanel for analytics
  • Deployed on Vercel; lint/typecheck as guardrails

The result

MCP Hub shipped in a weekend and feels coherent. AI didn't make choices for me—it just removed the slog. If you've got an idea, pairing with Codex is the quickest way I know to turn it into a real, working site.