qingflow-mcp 0.3.13 → 0.3.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +2 -2
  2. package/dist/server.js +795 -103
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -108,7 +108,7 @@ npm i -g git+https://github.com/853046310/qingflow-mcp.git
108
108
  Install from npm (pinned version):
109
109
 
110
110
  ```bash
111
- npm i -g qingflow-mcp@0.3.13
111
+ npm i -g qingflow-mcp@0.3.14
112
112
  ```
113
113
 
114
114
  Or one-click installer:
@@ -214,7 +214,7 @@ For `qf_query(summary)` and `qf_records_aggregate`, read `data.summary.completen
214
214
  1. `raw_scan_complete=false`: source data is not fully scanned, do not produce a final conclusion.
215
215
  2. `scan_limit_hit=true`: query stopped because scan budget was hit.
216
216
  3. `output_page_complete=false`: source may be complete, but output was truncated by `max_rows` or `max_groups`.
217
- 4. `raw_next_page_token`: use this token to continue raw scan pagination (`next_page_token` remains as a backward-compatible alias).
217
+ 4. `raw_next_page_token`: use this token to continue raw scan pagination (`next_page_token` remains as a backward-compatible alias). For `qf_query(summary)` / `qf_records_aggregate`, the token carries cumulative state, so keep query arguments unchanged when resuming.
218
218
 
219
219
  ## List Query Tips
220
220