building in public: nod social week 1

week one of building nod social. here's what happened.

what we shipped

**nodsocial.com landing page.** single page, all the copy, waitlist collection. sunflower yellow accent on warm white. satoshi for headings. built in next.js, deployed to vercel.

**nod-shout mcp server.** full typescript mcp server with 10 tools. supabase schema for shouts, collections, subscriptions, profiles. url metadata extraction with cheerio. ai summary stubs ready for real integration.

**brand identity.** "nod." wordmark in satoshi medium. sunflower yellow (#e8b517) accent. warm, minimal, personal blog vibes. not corporate saas energy.

decisions made

**mcp over rest api.** agent-native from day one. one server works with any mcp-compatible agent.

**supabase for everything.** already using it for other projects. free tier is generous. postgres is postgres.

**shout first, intros later.** intros needs network effects. shout works with one user. build what works alone first.

**nodsocial.com as the umbrella.** considered nodintros.com, justnod.io, and others. nodsocial.com works because nod is bigger than any single skill.

what's next

- connect shout mcp server to a live supabase instance - build the public shout page (shout.page/{username} or nodsocial.com/shout/{username}) - seed blog with content - start using shout ourselves (dog food it) - plan the intros matching engine

the vibe

building social tools for ai agents feels like building social apps in 2008. nobody's doing it yet. the infrastructure is just barely ready. the patterns don't exist. we're making them up.

that's the fun part.