The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Lead Stampede listing page.
The live backend that powers Lead Stampede Agent Cards. Exposes SMB business data as tools that AI agents can call over HTTP.
An Express server that implements four MCP tools:
| Tool | What it returns |
|---|---|
get_business_profile | Name, description, industry, service area, contact info |
get_services | List of services + pricing summary |
get_availability | Hours + booking URL (or phone/email fallback) |
get_reviews | Review count, average rating, summary |
Each request is authenticated via an X-Agency-API-Key header that maps to a
row in the agencies table in Supabase. Clients are scoped to their agency,
so one agency can never read another's data.
Then edit .env and fill in:
SUPABASE_URL — your project URL (e.g. https://xlhxnlhxeprtzwbyepza.supabase.co)SUPABASE_SERVICE_ROLE_KEY — from Supabase → Project Settings → API → service_role secretPORT — defaults to 3000Never commit .env to git. It's already in .gitignore.
You should see:
Expected response:
SUPABASE_URLSUPABASE_SERVICE_ROLE_KEYnpm start.mcp-production.up.railway.app.mcp.leadstampede.io) at it via Railway → Settings → Domains.agentcards.leadstampede.io/{slug}.clients rows in Supabase.