Why

MCP is the de facto agent-tool protocol. Once huddlz has an MCP server, any Claude/Cursor/ChatGPT user can ask their assistant about huddlz without us building UI for them. This is the distribution play.

Scope (MVP)

• MCP server (likely Elixir-native; tidewave has prior art, AshAi has tool extraction)
• Anonymous tools first: `search_groups`, `search_huddlz`, `get_huddlz_tonight`, `get_huddlz_this_weekend`, `get_groups_by_category`
• Authenticated tools (require user OAuth/API key): `rsvp_huddl`, `cancel_rsvp`, `join_group`, `leave_group`, `my_upcoming_huddlz`
• Tool descriptions written for LLM consumption (clear, semantic, no internal jargon)
• Auth: per-user API tokens issued from /profile, scoped (read-only vs. read-write)
• Rate limiting per token

Depends on

• Action audit (descriptions/argument shapes ready for tools)
• Categories (semantic args)
• Embeddings (semantic-search tools to feel magical)