@genlobe/mcp-server 3.6.1 → 3.6.2

package/dist/index.js

@@ -2069,6 +2069,30 @@ const END_USER_ENDPOINTS = {
                 },
                 notes: "Three modes (#178 + #350): (1) sk_live_* alone -> tenant-scoped record, created_by_id is NULL (catalog/blog/global config). (2) sk_live_* + end-user JWT -> user-scoped record, created_by_id = user.id (server-side caller acting on behalf of a user). (3) pk_live_* + end-user JWT -> user-scoped record, created_by_id = user.id (canonical 'two-phase' frontend pattern: pk in the browser, JWT after login). pk_live_* WITHOUT a JWT is rejected with 401 — a public key alone is anonymous and can't be the creator of a record."
             },
+            {
+                method: "POST",
+                path: "/v1/entity/records/bulk",
+                summary: "Bulk-insert up to 500 records into one schema in one transaction (migration-friendly)",
+                auth: { api_key: "sk_live_* or pk_live_*", jwt: "optional (same modes as POST /v1/entity/records)", headers: "X-Organization-Id required when key is not organization-scoped" },
+                request_body: {
+                    schema_id: "uuid (required) - all records in the batch target this schema",
+                    records: "array (required) - up to 500 JSON objects. Each is validated against the schema's fields_definition and reference fields (ADR-0009)."
+                },
+                notes: "All-or-nothing transaction: if ANY record fails schema or reference validation, the entire batch is rejected and nothing is persisted. Per-record errors include `record_index` so the agent can fix specific rows and retry. Capped at 500 records per call — for larger migrations, chunk the source dataset. Designed for Supabase → Genlobe table migrations (one source table → one custom_data_schema → one or more bulk chunks). Plan limits are checked once against the batch size; the whole batch fits or the whole batch fails. created_by_id follows the same rule as POST /v1/entity/records (NULL for sk_live_* alone, user.id when an end-user JWT is attached) and is identical for every row in the batch.",
+                example_request: `{
+  "schema_id": "550e8400-e29b-41d4-a716-446655440000",
+  "records": [
+    { "name": "Sugar 1kg", "price": 2.5, "stock": 100 },
+    { "name": "Rice 1kg", "price": 3.0, "stock": 50 },
+    { "name": "Coffee 250g", "price": 6.75, "stock": 30 }
+  ]
+}`,
+                example_response: `{
+  "schema_id": "550e8400-e29b-41d4-a716-446655440000",
+  "inserted_count": 3,
+  "items": [ { "id": "...", "schema_id": "...", "organization_id": "...", "data": {...} }, ... ]
+}`
+            },
             {
                 method: "GET",
                 path: "/v1/entity/records/mine",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@genlobe/mcp-server",
-  "version": "3.6.1",
+  "version": "3.6.2",
   "description": "MCP Server for GenLobe SaaS API - Provides AI assistants with comprehensive API documentation for building frontend applications",
   "main": "dist/index.js",
   "bin": {