@josephyan/qingflow-app-builder-mcp 1.1.2 → 1.1.3

package/README.md

@@ -3,13 +3,13 @@
 Install:
 
 ```bash
-npm install @josephyan/qingflow-app-builder-mcp@1.1.2
+npm install @josephyan/qingflow-app-builder-mcp@1.1.3
 ```
 
 Run:
 
 ```bash
-npx -y -p @josephyan/qingflow-app-builder-mcp@1.1.2 qingflow-app-builder-mcp
+npx -y -p @josephyan/qingflow-app-builder-mcp@1.1.3 qingflow-app-builder-mcp
 ```
 
 Environment:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@josephyan/qingflow-app-builder-mcp",
-  "version": "1.1.2",
+  "version": "1.1.3",
   "description": "Builder MCP for Qingflow app/package/system design and staged solution workflows.",
   "license": "MIT",
   "type": "module",

package/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "qingflow-mcp"
-version = "1.1.2"
+version = "1.1.3"
 description = "User-authenticated MCP server for Qingflow"
 readme = "README.md"
 license = "MIT"

package/skills/qingflow-app-builder/SKILL.md

@@ -87,6 +87,7 @@ Treat these as the official surface. Do not default to `package_create`, `packag
   - advanced bindings may use `button_limit`, `button_formula`, `button_formula_type`, and `print_tpls` only when visibility or print-template behavior is required
 - Associated resources:
   - `app_associated_resources_apply` is the public write path for the Qingflow app-level associated report/view pool and per-view display config
+  - for multi-app systems, use `apps[]` to batch associated-resource writes; each item carries its own `app_key` plus `upsert_resources` / `patch_resources` / `view_configs`
   - it attaches existing BI reports/views for in-app display; it does not create or edit QingBI report bodies/configs, including dataset reports
   - use `patch_resources` for changing match rules or other existing associated-resource parameters; the tool preserves backend-required raw fields internally
   - `associated_item_id` is the backend internal associated-resource id; for `view_configs`, `remove_associated_item_ids`, and `reorder_associated_item_ids`, you may pass `associated_item_id` or an existing resource's `chart_id`/`chart_key`/`view_key`, and the tool resolves it to the internal id

package/skills/qingflow-app-builder/references/tool-selection.md

@@ -52,7 +52,7 @@ These execute normalized patches. Some app apply tools publish by default and st
 - `app_flow_apply`: replace full workflow spec; use `patch_nodes[]` (`{id, set, unset}`) to update specific nodes without rewriting the full spec
 - `app_views_apply`: use `patch_views` for existing-view parameter replacement; use `upsert_views` for creation or full target config; remove views by key; new views default associated report/view display to visible with `limit_type="all"`; use `apps[]` for multi-app batch
 - `app_custom_buttons_apply`: use `patch_buttons` for existing-button parameter replacement; use `upsert_buttons` for creation or full target config; configure add-data field mappings/default values; bind buttons to header/detail/list view positions; `placement=list` maps to the backend `INSIDE` row/list button position; merge-mode view configs require `buttons`; use `view_configs[].mode="replace"` or `buttons=[]` to clear a view's custom button bindings. For child-record creation linked to the current source record, map `source_field: "数据ID"` to the target relation field. Use `apps[]` for multi-app batch.
-- `app_associated_resources_apply`: attach existing BI reports/views to the Qingflow app associated-resource pool and per-view display area; it does not create or edit QingBI report bodies/configs. Use `patch_resources` for existing associated-resource parameter replacement; use `upsert_resources` for creation or full target config; `view_configs`, remove, and reorder may reference existing resources by internal `associated_item_id` or by `chart_id`/`chart_key`/`view_key`; use `match_mappings` for associated view/report filters; publishes after successful writes; omit raw `sourceType`, and use `report_source="dataset"` only to attach an existing BI dataset report. Before `upsert_resources`, read `app_get.associated_resources` and reuse an existing matching `target_app_key + view_key/chart_key`; repeated upsert can create duplicates because `client_key` is only valid inside one apply call.
+- `app_associated_resources_apply`: attach existing BI reports/views to the Qingflow app associated-resource pool and per-view display area; it does not create or edit QingBI report bodies/configs. Use `patch_resources` for existing associated-resource parameter replacement; use `upsert_resources` for creation or full target config; `view_configs`, remove, and reorder may reference existing resources by internal `associated_item_id` or by `chart_id`/`chart_key`/`view_key`; use `match_mappings` for associated view/report filters; publishes after successful writes; omit raw `sourceType`, and use `report_source="dataset"` only to attach an existing BI dataset report. Before `upsert_resources`, read `app_get.associated_resources` and reuse an existing matching `target_app_key + view_key/chart_key`; repeated upsert can create duplicates because `client_key` is only valid inside one apply call. Use `apps[]` for multi-app batch.
 - `app_charts_apply`: create/edit/remove/reorder app-source QingBI report bodies/configs with `dataSourceType=qingflow`; it does not create/edit dataset BI reports and does not attach reports to Qingflow app associated-resource display. Use `patch_charts` for existing-chart parameter replacement; use `upsert_charts` for creation or full target config; supports `target/table` aliases plus QingBI chart types such as `summary`, `columnar`, `area`, `funnel`, `radar`, `scatter`, `dualaxes`, and `map`; charts are immediate-live and do not publish; use `chart_id` when names are not unique; use `apps[]` for multi-app batch
 - `portal_apply`: create or replace-update portal pages; use `dash_key` for update mode or `package_id + dash_name` for create mode; edit mode may omit `sections` for base-info-only updates; when sections are supplied they still use replace semantics; sections use a 24-column PC grid — all components in the same row (same `y`) must share the same `rows` value and their `cols` must sum to exactly 24; mismatched `rows` causes height misalignment, `cols` under 24 leaves trailing blank space; use `patch_sections[]` (`{chart_ref/view_ref/order, set, unset}`) to update individual sections without replacing all
 

package/src/qingflow_mcp/builder_facade/service.py

@@ -5486,6 +5486,9 @@ class AiBuilderFacade:
         result = []
         for c in components:
             item = {k: v for k, v in c.items() if k != "order"}
+            position = item.get("position")
+            if isinstance(position, dict):
+                item["position"] = _portal_component_position_for_request(position)
             result.append(item)
         return result
 
@@ -14180,6 +14183,27 @@ def _portal_position_payload(position: Any, *, inferred_mobile_y: int = 0) -> di
     }
 
 
+def _portal_component_position_for_request(position: dict[str, Any]) -> dict[str, Any]:
+    """Normalize portal_get component positions into PortalSectionPatch input shape."""
+    payload = deepcopy(position)
+    if isinstance(payload.get("pc"), dict) or isinstance(payload.get("mobile"), dict):
+        return payload
+    pc_keys = {"x", "y", "cols", "rows"}
+    if any(key in payload for key in pc_keys):
+        pc = {
+            "x": int(payload.get("x") or 0),
+            "y": int(payload.get("y") or 0),
+            "cols": int(payload.get("cols") or payload.get("w") or 12),
+            "rows": int(payload.get("rows") or payload.get("h") or 8),
+        }
+        normalized: dict[str, Any] = {"pc": pc}
+        mobile = payload.get("mobile")
+        if isinstance(mobile, dict):
+            normalized["mobile"] = mobile
+        return normalized
+    return payload
+
+
 def _portal_component_position_public(
     source_type: Any,
     *,

package/src/qingflow_mcp/cli/commands/builder.py

@@ -166,12 +166,13 @@ def register(subparsers: argparse._SubParsersAction[argparse.ArgumentParser]) ->
     associated_resource_get.set_defaults(handler=_handle_associated_resource_get, format_hint="builder_summary")
 
     associated_resource_apply = associated_resource_subparsers.add_parser("apply", help="声明式管理应用关联资源池和视图展示配置")
-    associated_resource_apply.add_argument("--app-key", required=True)
+    associated_resource_apply.add_argument("--app-key", default="")
     associated_resource_apply.add_argument("--upsert-resources-file")
     associated_resource_apply.add_argument("--patch-resources-file")
     associated_resource_apply.add_argument("--remove-associated-item-ids-file")
     associated_resource_apply.add_argument("--reorder-associated-item-ids-file")
     associated_resource_apply.add_argument("--view-configs-file")
+    associated_resource_apply.add_argument("--apps-file", help="多应用批量关联资源 JSON 数组，每项含 app_key + upsert_resources/patch_resources/remove_associated_item_ids/reorder_associated_item_ids/view_configs")
     associated_resource_apply.set_defaults(handler=_handle_associated_resource_apply, format_hint="builder_summary", force_json_output=True)
 
     portal = builder_subparsers.add_parser("portal", help="门户")
@@ -456,6 +457,36 @@ def _handle_button_apply(args: argparse.Namespace, context: CliContext) -> dict:
 
 
 def _handle_associated_resource_apply(args: argparse.Namespace, context: CliContext) -> dict:
+    apps = load_list_arg(getattr(args, "apps_file", None), option_name="--apps-file")
+    if apps:
+        single_app_args = [
+            a for a in [
+                "--app-key" if args.app_key else None,
+                "--upsert-resources-file" if getattr(args, "upsert_resources_file", None) else None,
+                "--patch-resources-file" if getattr(args, "patch_resources_file", None) else None,
+                "--remove-associated-item-ids-file" if getattr(args, "remove_associated_item_ids_file", None) else None,
+                "--reorder-associated-item-ids-file" if getattr(args, "reorder_associated_item_ids_file", None) else None,
+                "--view-configs-file" if getattr(args, "view_configs_file", None) else None,
+            ] if a
+        ]
+        if single_app_args:
+            raise_config_error(
+                f"associated-resource apply --apps-file cannot be combined with {', '.join(single_app_args)}.",
+                fix_hint="Use --apps-file for batch mode (each item contains app_key + per-app params), or remove --apps-file for single-app mode.",
+            )
+    if apps:
+        return context.builder.app_associated_resources_apply(
+            profile=args.profile,
+            app_key="",
+            upsert_resources=[],
+            patch_resources=[],
+            remove_associated_item_ids=[],
+            reorder_associated_item_ids=[],
+            view_configs=[],
+            apps=apps,
+        )
+    if not args.app_key:
+        raise_config_error("associated-resource apply requires --app-key or --apps-file", fix_hint="Pass --app-key APP_KEY for single-app mode, or --apps-file for batch mode.")
     return context.builder.app_associated_resources_apply(
         profile=args.profile,
         app_key=args.app_key,

package/src/qingflow_mcp/tools/ai_builder_tools.py

@@ -284,6 +284,7 @@ class AiBuilderTools(ToolBase):
             remove_associated_item_ids: list[int] | None = None,
             reorder_associated_item_ids: list[int] | None = None,
             view_configs: list[JSONObject] | None = None,
+            apps: list[JSONObject] | None = None,
         ) -> JSONObject:
             return self.app_associated_resources_apply(
                 profile=profile,
@@ -293,6 +294,7 @@ class AiBuilderTools(ToolBase):
                 remove_associated_item_ids=remove_associated_item_ids or [],
                 reorder_associated_item_ids=reorder_associated_item_ids or [],
                 view_configs=view_configs or [],
+                apps=apps,
             )
 
         @mcp.tool()
@@ -1120,8 +1122,24 @@ class AiBuilderTools(ToolBase):
         reorder_associated_item_ids: list[int],
         view_configs: list[JSONObject],
         patch_resources: list[JSONObject] | None = None,
+        apps: list[JSONObject] | None = None,
     ) -> JSONObject:
         """执行应用关联资源 apply 逻辑。"""
+        if apps:
+            return self._facade._batch_write_apps(
+                profile=profile,
+                apps=apps,
+                single_writer=lambda profile, app_key, **kw: self.app_associated_resources_apply(
+                    profile=profile,
+                    app_key=app_key,
+                    upsert_resources=kw.get("upsert_resources", []),
+                    patch_resources=kw.get("patch_resources", []),
+                    remove_associated_item_ids=kw.get("remove_associated_item_ids", []),
+                    reorder_associated_item_ids=kw.get("reorder_associated_item_ids", []),
+                    view_configs=kw.get("view_configs", []),
+                ),
+                tool_name="app_associated_resources_apply",
+            )
         raw_request = {
             "app_key": app_key,
             "upsert_resources": upsert_resources,
@@ -4458,6 +4476,7 @@ _BUILDER_TOOL_CONTRACTS: dict[str, JSONObject] = {
     "app_associated_resources_apply": {
         "allowed_keys": [
             "app_key",
+            "apps",
             "upsert_resources",
             "patch_resources",
             "remove_associated_item_ids",
@@ -4527,6 +4546,7 @@ _BUILDER_TOOL_CONTRACTS: dict[str, JSONObject] = {
             "if an associated resource delete returns readback_status=unavailable or still_exists, treat the result as readback pending and do not blindly repeat the delete",
             "this tool publishes after at least one write succeeds; there is no draft-only mode",
             "visible=false hides the associated-resource area without clearing previous selected ids; visible=true with limit_type=all shows the whole app-level pool",
+            "accepts apps[] for multi-app batch; each item is {app_key, upsert_resources?, patch_resources?, remove_associated_item_ids?, reorder_associated_item_ids?, view_configs?}",
         ],
         "minimal_example": {
             "profile": "default",
@@ -4557,6 +4577,22 @@ _BUILDER_TOOL_CONTRACTS: dict[str, JSONObject] = {
                 }
             ],
         },
+        "batch_example": {
+            "profile": "default",
+            "apps": [
+                {
+                    "app_key": "APP_1",
+                    "upsert_resources": [
+                        {"client_key": "orders_view", "graph_type": "view", "target_app_key": "ORDER_APP", "view_key": "ORDER_VIEW"}
+                    ],
+                    "view_configs": [{"view_key": "MAIN_VIEW", "limit_type": "select", "associated_item_refs": ["orders_view"]}],
+                },
+                {
+                    "app_key": "APP_2",
+                    "view_configs": [{"view_key": "MAIN_VIEW", "visible": True, "limit_type": "all"}],
+                },
+            ],
+        },
     },
     "app_schema_plan": {
         "allowed_keys": ["app_key", "package_id", "app_name", "icon", "color", "visibility", "create_if_missing", "add_fields", "update_fields", "remove_fields"],
@@ -5552,7 +5588,7 @@ _BUILDER_TOOL_CONTRACTS: dict[str, JSONObject] = {
             "call workspace_icon_catalog_get or `qingflow --json builder icon catalog` for supported icon/color candidates",
             "portal_apply uses replace semantics for sections",
             "when editing an existing portal, sections may be omitted to update only base info such as visibility, icon, or package",
-            "use patch_sections[] for targeted section updates without replacing all sections; each item needs one selector (chart_ref with chart_id/chart_key/chart_name, view_ref with view_key/view_name, or order as 0-based index) plus set/unset",
+            "use patch_sections[] for section-level patch updates without replacing all sections; each item needs one selector (chart_ref with chart_id/chart_key/chart_name, view_ref with view_key/view_name, or order as 0-based index) plus set/unset",
             "when sections[] is supplied without patch_sections[], it uses replace semantics for all sections",
             "remove a section by omitting it from the sections list (replace mode) or by unset in patch_sections (patch mode)",
             "package_id is required when creating a new portal",