¶ Main project (hc-portal data)
- hc-portal — primary database (Prisma ORM)
- hc-evidence — HubSpot deals + Stripe data (synced by hc-knowledge-mcp cron on hc-central)
- hc-knowledge-mcp — reads portal data for knowledge corpus
| Table |
Synced from |
Used by Evidence |
next_hubspot_deals |
HubSpot API (via hc-sync) |
Growth reports |
next_stripe_charges |
Stripe API (via hc-sync) |
Finance/stripe_charges |
next_stripe_payment_intents |
Stripe API (via hc-sync) |
Finance reports |
- hc-knowledge-mcp — stores ingested documents, chunk metadata, source tracking
- Qdrant handles the actual vector storage; Supabase stores the relational metadata
All connection strings and keys are in credentials.sops.yaml under supabase.main and supabase.knowledge.
# Quick access
sops -d credentials.sops.yaml | grep -A5 "supabase:"