Skip to content
docs
UseBuildChangelog
Open Lumin

Examples

Nine apps built on the use-case catalog

Each app is a server route, the Lumin MCP endpoint with a deny-by-default tool allowlist, and a structured JSON response your own UI renders. No chat surface. The apps are chosen to exercise as much of the tool catalog as possible, leading with the two input classes that need no personal data at all.

Every app on this page is open source and MIT licensed at github.com/dinethlive/lumin-examples. One npm install covers all nine.

AppPitchVerticalInput classFamilies exercisedCalls
wellness-matcherAyurvedic prakriti read plus 4 product picks for a D2C wellness brand.Wellness, Ayurveda and beautyNatalChart foundation, Ayurvedic constitution, planetary strength~9
products-matcherConsumer personality read plus 5 picks from a generalist e-commerce catalog.Commerce and personalizationNatalChart foundation, Jaimini, divisional (D2), strength~11
health-risk-analyzerConstitutional health risk profile across 8 body systems, for telehealth and wellness platforms.Wellness and healthNatalFoundation, promise, significators, multi-system verdict, dasha, transit, divisional, health~29
weather-windowsRoughly 14-day weather-lens windows across a date range, for a place.Place-based and operationsPlace and date. Zero PIIAstrometeorology4 to 5
today-panelDaily panchang, choghadiya and hora panel for any city.Local services and productivityPlace and date. Zero PIIPanchang, muhurta adjuncts, moon transit, sub-lord changes5
horary-deskAsk a question, pick a number 1 to 249, get an answer, or an honest refusal.Horary, cross-verticalHorary. Zero PIIHorary4 to 6
muhurta-schedulerElectional date picker over the named event catalog.Scheduling and electionalNatal plus a rangeElectional, panchang5 to 7
kundli-matchThree compatibility systems computed on the same two charts, side by side.Matrimonial and datingTwo-personCompatibility, doshas, promise, chart integrity10 to 14
career-fitVocational fit, quit-or-stay, promotion prep and exam-window timing in one report.Career and educationNatalCareer, education8 to 10 metered

The pattern every app shares

A server route validates the input, calls a shared Lumin client with a fixed allowlist of tool names, a system prompt that owns the business logic, and a user prompt built from the request. The client streams the model's final text block, and the route parses one JSON object out of it, validates its shape, and returns it. No app renders a chat bubble; the model never appears in the product.

The business logic (which tools to call, how to map a chart signal to a product decision, the disclaimer wording) lives in each app's system prompt. The Lumin MCP tools stay generic. Fork any of these, change the prompt and the catalog, ship a different vertical.

Source

These apps live in a separate repository, not yet published. This page documents their shape so you can build the same pattern today against the public MCP endpoint; the repository link will be added here once it is public.

Where to next

  • Recipes for the patterns that cut across every app: tool allowlisting, paging to exhaustion, the composite-versus-expanded tradeoff, cross-system labelling, and the chart-integrity gate.
  • Use cases for the full catalog these nine apps are drawn from.
  • Integrate into your app for the chat-surface pattern these examples deliberately do not use.