@enfyra/mcp-server 0.0.33 → 0.0.34

package/package.json

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

package/src/lib/mcp-examples.js

@@ -553,7 +553,7 @@ create_extension({
   name: "ReportsPage",
   description: "Reports dashboard",
   menuId: "<created-menu-id>",
-  code: "<template><section class=\\"min-h-full w-full p-4 sm:p-6 lg:p-8\\">Reports</section></template><script setup>useHeaderActionRegistry({ id: 'refresh-reports', label: 'Refresh', icon: 'lucide:refresh-cw', onClick: () => {}, order: 0 })</script>",
+  code: "<template><section class=\\"min-h-full w-full space-y-4\\">Reports</section></template><script setup>useHeaderActionRegistry({ id: 'refresh-reports', label: 'Refresh', icon: 'lucide:refresh-cw', onClick: () => {}, order: 0 })</script>",
   isEnabled: true
 })`,
         notes: [
@@ -561,6 +561,7 @@ create_extension({
           'Use menu_definition.label, not title.',
           'For page extensions, create the menu first and pass menuId to create_extension.',
           'Page extensions should be full-bleed by default and responsive from the first version.',
+          'The extension root is already inside eApp main; do not add root-level page padding.',
         ],
       },
       {
@@ -576,17 +577,20 @@ create_menu({
 })
 
 // Child page extensions should be focused:
-// /dashboard            overview with time range KPIs
+// /dashboard            compact summary/routing hub: KPIs, current signal, attention queue, navigation cards
 // /cloud/projects      project status and drill-downs
 // /cloud/provisioning  provisioning timeline/failures/slow steps
 // /cloud/billing       orders/subscriptions/refunds
 // /cloud/infrastructure hosts/capacity/plans/system credential readiness
 // /cloud/readiness     legal/Paddle/landing launch checklist
-// Use UTabs inside large pages instead of placing every section in one dashboard.`,
+// Use UTabs inside large pages instead of placing every section in one dashboard.
+// For admin record management, link to /data/<table>, e.g. /data/landing_terms, not public landing paths.`,
         notes: [
           'Design the menu/page split before generating dashboard code.',
-          'Keep /dashboard as overview and use focused pages for operational domains.',
+          'Keep /dashboard as a summary and distribution page, not a detailed operations table.',
+          'Use focused pages for operational domains.',
           'UTabs is available in eApp extension runtime for page-level sections.',
+          'Admin links for editing or inspecting records should point to /data/<table> routes.',
         ],
       },
       {

package/src/lib/mcp-instructions.js

@@ -271,8 +271,9 @@ export function buildMcpServerInstructions(apiBaseUrl) {
     '- **CRITICAL:** MUST call `create_record` or `update_record` on `extension_definition` — outputting Vue code in chat does NOT save it. User will NOT see it.',
     '- **Code format:** Vue SFC only. Structure: `<template>...</template>` + `<script setup>...</script>`. Server auto-compiles; if compile fails, fix and retry.',
     '- **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 overview; create focused menu pages for projects, provisioning, billing, infrastructure, and readiness when the surface grows.',
-    '- **Page layout default:** page extensions should render full-bleed inside the app shell by default. 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.',
+    '- **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.',
+    '- **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.',
     '',
     '#### Injected Vue API functions:',