@dypai-ai/mcp 1.1.0 → 1.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dypai-ai/mcp",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "DYPAI MCP Server — AI agent toolkit for building and deploying full-stack apps",
   "type": "module",
   "main": "src/index.js",

package/src/index.js

@@ -37,12 +37,12 @@ import { bulkUpsertTool } from "./tools/bulk-upsert.js"
 // for the agent. The implementation still lives at ./tools/sync/describe.js
 // in case we want to resurrect it as a read-only peek for multi-project flows.
 import { dypaiPullTool, dypaiDiffTool, dypaiPushTool, dypaiValidateTool, dypaiTestEndpointTool } from "./tools/sync/index.js"
-// dypaiCodegenTool is intentionally NOT imported here — codegen runs
-// automatically on dypai_pull / dypai_push / schema-affecting execute_sql.
-// The standalone tool would duplicate that path and could confuse the agent
-// into calling it needlessly. The helper `regenerateTypes` in ./tools/codegen.js
-// is still used internally by those triggers.
-// import { dypaiCodegenTool } from "./tools/codegen.js"
+// Codegen removed from v1 entirely — neither the standalone tool nor the
+// auto-triggers on pull/push/DDL are wired in. The agent reads dypai/schema.sql
+// and endpoint YAMLs directly and casts at the frontend edge when needed
+// (same mental model as using raw Supabase without the CLI-generated types).
+// The ./tools/codegen.js file is preserved on disk in case v2 re-introduces a
+// leaner version that only emits the Database type without wrappers.
 import { proxyToolCall } from "./tools/proxy.js"
 import { enrichSuccess, enrichError } from "./tools/enrich.js"
 import { maybeRefreshSchemaAfterExecuteSql } from "./tools/sql-side-effects.js"
@@ -75,7 +75,7 @@ const LOCAL_TOOLS = [
   dypaiPushTool,
   dypaiTestEndpointTool,
   // dypaiTestTool (YAML test-suite runner) — hidden until v2. See import comment above.
-  // dypaiCodegenTool hidden — runs automatically on pull/push/DDL.
+  // dypaiCodegenTool removed from v1 — see codegen import comment above.
 ]
 
 const localToolMap = new Map(LOCAL_TOOLS.map(t => [t.name, t]))
@@ -162,7 +162,7 @@ const SERVER_INSTRUCTIONS = `You are building full-stack applications on the DYP
 
 ## Getting Started
 1. Call list_projects() to find your project_id (skip if you already know it).
-2. **ALWAYS CALL dypai_pull FIRST** on any project you haven't worked on in this session. It materializes ./dypai/ (endpoints, SQL, prompts, code, schema.sql, node-catalog.json, realtime.yaml), regenerates TS types under src/dypai/, and returns an \`overview\` block with endpoint groups, credentials, and tool-enabled endpoints — everything you need to orient yourself in one call.
+2. **ALWAYS CALL dypai_pull FIRST** on any project you haven't worked on in this session. It materializes ./dypai/ (endpoints, SQL, prompts, code, schema.sql, node-catalog.json, realtime.yaml) and returns an \`overview\` block with endpoint groups, credentials, and tool-enabled endpoints — everything you need to orient yourself in one call.
 3. BEFORE implementing an unfamiliar feature, call search_docs with the topic (e.g. "auth", "upload files", "realtime", "stripe").
 4. Build backend first, then frontend.
 
@@ -251,7 +251,7 @@ When you hit a red flag, replace the JS node. When the JS legitimately does more
 - dypai/tests/*.test.yaml — reserved for the v2 suite runner; leave empty for now
 - dypai/dypai.config.yaml — project identity (don't hand-edit)
 - dypai/.dypai/ — local cache (gitignored)
-- src/dypai/ — auto-generated TS types (Database + typed api wrapper). Auto-refreshed on pull/push/DDL.
+- src/dypai/ — NOT auto-generated. If you want TS types for row shapes in the frontend, define them manually based on dypai/schema.sql (a codegen helper may return in a future version).
 - All *_file paths inside YAML are relative to dypai/ root (not to the YAML file).
 
 ## Build Frontend

package/src/tools/sql-side-effects.js

@@ -13,7 +13,8 @@ import { writeFile } from "fs/promises"
 import { join, isAbsolute, dirname, delimiter } from "path"
 import { homedir } from "os"
 import { dumpPublicSchema } from "./sync/schema-dump.js"
-import { regenerateTypes } from "./codegen.js"
+// Codegen removed from v1. If we reintroduce TS type generation we'd call it here.
+// import { regenerateTypes } from "./codegen.js"
 
 // Matches CREATE/ALTER/DROP/TRUNCATE/RENAME on TABLE — the only DDL shapes we
 // currently reflect in schema.sql. CREATE INDEX / FUNCTION / TYPE are skipped.
@@ -79,16 +80,9 @@ export async function maybeRefreshSchemaAfterExecuteSql(args, result) {
     const target = join(dypaiDir, "schema.sql")
     await writeFile(target, newSchema, "utf8")
 
-    // Schema changed → frontend TS types need to follow. Best-effort.
-    let codegen
-    try { codegen = await regenerateTypes(dypaiDir) }
-    catch (e) { codegen = { skipped: true, reason: e.message } }
-
     return {
       refreshed: true,
       path: target,
-      types_regenerated: !!codegen?.regenerated,
-      types_output: codegen?.output_dir,
     }
   } catch (e) {
     // Don't fail the execute_sql call itself — just report the side-effect failure.

package/src/tools/sync/pull.js

@@ -19,7 +19,10 @@ import YAML from "yaml"
 import { proxyToolCall } from "../proxy.js"
 import { serializeEndpoint } from "./codec.js"
 import { dumpPublicSchema } from "./schema-dump.js"
-import { regenerateTypes } from "../codegen.js"
+// Codegen was removed from v1 — the agent reads dypai/schema.sql + endpoint YAMLs
+// directly instead of relying on auto-generated TS types. The codegen.js file
+// still lives on disk in case we resurface it later with a leaner design.
+// import { regenerateTypes } from "../codegen.js"
 
 /**
  * Resolve a user-supplied out_dir. When an IDE spawns this MCP over stdio, the
@@ -352,10 +355,7 @@ export const dypaiPullTool = {
     }
     await writeFileEnsured(join(outDir, ".dypai", "state.json"), JSON.stringify(state, null, 2) + "\n")
 
-    // Auto-regenerate TS types for the frontend (src/dypai/). Non-fatal on failure.
-    let codegen
-    try { codegen = await regenerateTypes(outDir) }
-    catch (e) { codegen = { skipped: true, reason: e.message } }
+    // Codegen removed from v1. If we reintroduce it, this is where it wires in.
 
     // Compact overview — replaces what dypai_describe used to print, but
     // derived from the data we already have in memory (zero extra queries).
@@ -397,9 +397,6 @@ export const dypaiPullTool = {
       output_dir: outDir,
       out_dir_resolved_via: outDirSource,
       overview,
-      codegen: codegen?.regenerated
-        ? { output_dir: codegen.output_dir, files: codegen.files_written.length }
-        : (codegen?.reason || undefined),
       errors: errors.length ? errors : undefined,
       warning: suspiciousWarning || undefined,
       hint: errors.length

package/src/tools/sync/push.js

@@ -21,7 +21,8 @@ import {
   localToCanonical,
 } from "./planner.js"
 import { runValidation } from "./validate.js"
-import { regenerateTypes } from "../codegen.js"
+// Codegen removed from v1 — see pull.js note.
+// import { regenerateTypes } from "../codegen.js"
 
 // ─── Apply helpers ─────────────────────────────────────────────────────────
 
@@ -357,18 +358,6 @@ export const dypaiPushTool = {
       errors.push({ op: "realtime", error: e.message })
     }
 
-    const changedNames = [
-      ...applied.created,
-      ...applied.updated.map(u => u.name),
-    ]
-
-    // Regenerate TS types if endpoints changed (input/output schemas may have shifted).
-    let codegen
-    if (changedNames.length > 0) {
-      try { codegen = await regenerateTypes(rootDir) }
-      catch (e) { codegen = { skipped: true, reason: e.message } }
-    }
-
     return {
       success: errors.length === 0,
       applied: true,
@@ -379,9 +368,6 @@ export const dypaiPushTool = {
         unchanged: plan.unchanged.length,
         errors: errors.length,
         realtime: realtime || { skipped: true, reason: "no realtime.yaml" },
-        codegen: codegen?.regenerated
-          ? { files: codegen.files_written.length }
-          : (codegen?.reason || "no changes to regenerate"),
       },
       details: applied,
       errors: errors.length ? errors : undefined,