@josephyan/qingflow-app-builder-mcp 0.2.0-beta.34 → 0.2.0-beta.36

package/README.md

@@ -3,13 +3,13 @@
 Install:
 
 ```bash
-npm install @josephyan/qingflow-app-builder-mcp@0.2.0-beta.34
+npm install @josephyan/qingflow-app-builder-mcp@0.2.0-beta.36
 ```
 
 Run:
 
 ```bash
-npx -y -p @josephyan/qingflow-app-builder-mcp@0.2.0-beta.34 qingflow-app-builder-mcp
+npx -y -p @josephyan/qingflow-app-builder-mcp@0.2.0-beta.36 qingflow-app-builder-mcp
 ```
 
 Environment:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@josephyan/qingflow-app-builder-mcp",
-  "version": "0.2.0-beta.34",
+  "version": "0.2.0-beta.36",
   "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 = "0.2.0b34"
+version = "0.2.0b36"
 description = "User-authenticated MCP server for Qingflow"
 readme = "README.md"
 license = "MIT"

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

@@ -17,6 +17,12 @@ Before any write or verification flow, identify whether the task targets `test`
 
 Pick the smallest tool layer that can finish the task.
 
+## Shared Helper
+
+- `feedback_submit` is a cross-cutting helper for product feedback submission
+- It does not require Qingflow login or workspace selection
+- If builder capability is unsupported or still cannot satisfy the need after reasonable use, summarize the gap, ask whether to submit feedback, and call `feedback_submit` only after explicit user confirmation.
+
 ## Mental Model
 
 Model builder requests in four layers. Do not flatten them.

package/src/qingflow_mcp/__init__.py

@@ -2,4 +2,4 @@ from __future__ import annotations
 
 __all__ = ["__version__"]
 
-__version__ = "0.2.0b34"
+__version__ = "0.2.0b36"

package/src/qingflow_mcp/config.py

@@ -13,6 +13,7 @@ DEFAULT_RECORD_LIST_TYPE = 8
 ATTACHMENT_QUESTION_TYPE = 13
 DEFAULT_BASE_URL = "https://qingflow.com/api"
 DEFAULT_FEEDBACK_APP_KEY = "e0d017kju002"
+DEFAULT_FEEDBACK_QSOURCE_TOKEN = "mcp-feedback-7755d14748fc"
 
 
 def get_mcp_home() -> Path:
@@ -142,7 +143,7 @@ def get_feedback_qsource_token() -> str | None:
     value = get_config_value(
         "feedback.qsource_token",
         env_var="QINGFLOW_MCP_FEEDBACK_QSOURCE_TOKEN",
-        default=None,
+        default=DEFAULT_FEEDBACK_QSOURCE_TOKEN,
     )
     if value is None:
         return None

package/src/qingflow_mcp/server.py

@@ -36,6 +36,14 @@ def build_server() -> FastMCP:
 Use `auth_login` first, then `workspace_list` and `workspace_select`.
 All resource tools operate with the logged-in user's Qingflow permissions.
 
+## Shared Helper
+
+`feedback_submit` is always available as a cross-cutting helper.
+
+- Use it when the current MCP capability is unsupported, awkward, or still cannot satisfy the user's need after reasonable use.
+- It does not require Qingflow login or workspace selection.
+- Call it only after the user explicitly confirms submission.
+
 ## App Discovery
 
 If `app_key` is unknown, use `app_list` or `app_search` first.

package/src/qingflow_mcp/server_app_builder.py

@@ -17,6 +17,7 @@ def build_builder_server() -> FastMCP:
         "Qingflow App Builder MCP",
         instructions=(
             "Use this server for AI-native Qingflow builder workflows. "
+            "`feedback_submit` is always available as a cross-cutting helper when the current capability is unsupported, awkward, or still cannot satisfy the user's need after reasonable use; it does not require Qingflow login or workspace selection, and it should be called only after explicit user confirmation. "
             "Follow the resource path resolve -> summary read -> plan -> apply -> attach -> publish_verify. "
             "Use builder_tool_contract when you need a machine-readable contract, aliases, allowed enums, or a minimal valid example for a public builder tool. "
             "If creating a new package may be appropriate, ask the user to confirm package creation before calling package_create; otherwise use package_resolve/package_list and app_resolve to locate resources, "

package/src/qingflow_mcp/server_app_user.py

@@ -28,6 +28,14 @@ def build_user_server() -> FastMCP:
 
 If `app_key` is unknown, use `app_list` or `app_search` first.
 
+## Shared Helper
+
+`feedback_submit` is always available as a cross-cutting helper.
+
+- Use it when the current MCP capability is unsupported, awkward, or still cannot satisfy the user's need after reasonable use.
+- It does not require Qingflow login or workspace selection.
+- Call it only after the user explicitly confirms submission.
+
 ## Schema-First Rule
 
 Always call `record_schema_get` before `record_list`, `record_get`, `record_write`, or `record_analyze`.

package/src/qingflow_mcp/tools/feedback_tools.py

@@ -46,6 +46,12 @@ class FeedbackTools:
             workflow_node_id: str | int | None = None,
             note: str | None = None,
         ) -> JSONObject:
+            """Submit product feedback to the Qingflow MCP team.
+
+            Use this when the current MCP capability is unsupported, awkward, or still cannot satisfy the user's need
+            after reasonable attempts. This helper writes through the internal q-source feedback intake, does not
+            require Qingflow login or workspace selection, and should be called only after explicit user confirmation.
+            """
             return self.feedback_submit(
                 category=category,
                 title=title,