@enfyra/mcp-server 0.0.35 → 0.0.37

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@enfyra/mcp-server",
-  "version": "0.0.35",
+  "version": "0.0.37",
   "description": "MCP server for Enfyra - manage your Enfyra instance via Claude Code",
   "type": "module",
   "license": "MIT",

package/src/lib/mcp-examples.js

@@ -590,6 +590,7 @@ create_menu({
           'Keep /dashboard as a summary and distribution page, not a detailed operations table.',
           'Use focused pages for operational domains.',
           'Provisioning pages should not show raw history rows as the primary UI; group by project/run and translate step keys into operator-facing labels.',
+          'Operational lists should use pagination plus search/filter controls; do not rely on arbitrary fixed limits such as limit=50.',
           'UTabs is available in eApp extension runtime for page-level sections.',
           'Admin links for editing or inspecting records should point to /data/<table> routes.',
         ],
@@ -633,6 +634,56 @@ console.log(ok, requiredTerms.has('cloud-terms'), loaded, label, date)
           'If diagnostics complain about these APIs, fix eApp extension TypeScript lib/runtime contract.',
         ],
       },
+      {
+        name: 'Dashboard aggregate stats with a time range',
+        code: `<script setup>
+const range = ref('7d')
+const now = () => new Date()
+const rangeStart = computed(() => {
+  const d = now()
+  if (range.value === '24h') d.setHours(d.getHours() - 24)
+  else if (range.value === '30d') d.setDate(d.getDate() - 30)
+  else d.setDate(d.getDate() - 7)
+  return d.toISOString()
+})
+
+const flowStats = useApi('/flow_execution_definition', {
+  query: computed(() => ({
+    fields: 'id',
+    limit: 1,
+    meta: 'filterCount',
+    filter: { startedAt: { _gte: rangeStart.value } },
+    aggregate: {
+      id: { count: true },
+      status: { count: { _eq: 'failed' } }
+    }
+  }))
+})
+
+const orderStats = useApi('/cloud_payment_orders', {
+  query: computed(() => ({
+    fields: 'id',
+    limit: 1,
+    meta: 'filterCount',
+    filter: { createdAt: { _gte: rangeStart.value } },
+    aggregate: {
+      id: { count: true },
+      status: { count: { _eq: 'applied' } },
+      amount_cents: { sum: { _gte: 0 } }
+    }
+  }))
+})
+
+watch(range, () => Promise.all([flowStats.execute(), orderStats.execute()]))
+onMounted(() => Promise.all([flowStats.execute(), orderStats.execute()]))
+</script>`,
+        notes: [
+          'Aggregate keys must be real fields or relations.',
+          'Read results from response.meta.aggregate.',
+          'Use top-level filter for time windows and cross-field conditions.',
+          'sum/avg require numeric fields; do not sum varchar money fields.',
+        ],
+      },
     ],
   },
 };

package/src/lib/mcp-instructions.js

@@ -273,6 +273,10 @@ export function buildMcpServerInstructions(apiBaseUrl) {
     '- **NO import statements.** All APIs are injected globally (see full list below).',
     '- **Design first for dashboards:** before creating/updating a dashboard extension, define the menu/page split, time range controls, tabs, and drill-down links. Keep `/dashboard` as a compact summary and routing hub only: KPIs, current signal, attention queue, and navigation cards. Put detailed lists/tables/timelines into focused pages such as projects, provisioning, billing, infrastructure, and readiness.',
     '- **Operational page modeling:** model admin operational pages around the operator mental entity, not raw database/event rows. For provisioning, group history by project/run, translate internal step keys into readable labels, show current step, operator meaning, and next action, and keep raw history as a secondary `/data` shortcut.',
+    '- **Operational list data loading:** do not use arbitrary fixed limits such as `limit=50` as the whole data strategy for admin pages. Use pagination, expose result count when the API supports `meta=filterCount`, and add search/filter controls for natural lookup keys such as project id, name, and subdomain.',
+    '- **ESV aggregate contract:** aggregate query must be an object keyed by a real field or relation, for example `aggregate: { id: { count: true }, status: { count: { _eq: "failed" } }, amount: { sum: true } }`. Results are returned in `response.meta.aggregate`. Time windows and cross-field conditions belong in top-level `filter`, not inside a field aggregate condition. Field aggregate conditions only support operators on that same field; relation aggregates use `countRecords`.',
+    '- **Aggregate numeric rule:** `sum` and `avg` require a numeric field in ESV. Do not aggregate money stored as varchar/text. Add/use a numeric amount field such as `amount_cents` or `amount` for revenue stats, or build a dedicated stats route that normalizes legacy values explicitly.',
+    '- **Dashboard stats:** time range buttons must change the query filter and reload stats. Cloud dashboard should summarize flow execution errors from `flow_execution_definition` and billing stats from order/subscription records; successful/no-error flow runs do not need a standalone provisioning menu.',
     '- **Page layout default:** page extensions should render full-bleed inside the app shell by default. The extension root is already inside the eApp page `<main>`, so do not add root-level page padding such as `p-4 sm:p-6 xl:p-8`; use spacing between internal sections only. Do not wrap the entire page in a centered card/container unless explicitly requested. Use responsive grids/stacks from the first version so the page works on desktop, tablet, and mobile.',
     '- **Admin record links:** when an admin extension links to backend records for management or inspection, point to eApp data routes such as `/data/landing_terms`, `/data/cloud_projects`, or `/data/cloud_payment_orders`. Do not use public landing-page paths from record fields such as `/cloud-terms` unless the explicit intent is previewing the public website.',
     '- **Do not downgrade extension code to ES5 to appease tooling.** eApp extension runtime should support normal browser/runtime APIs such as `Array.includes`, `Set`, `Promise.all`, `String.replace`, `Intl.DateTimeFormat`, and `Intl.NumberFormat`. If diagnostics reject these, fix eApp extension checker/runtime contract instead of rewriting generated extension code around the limitation.',