Follow-up to #107: /v1/coding_plan/search API needs pagination support

Follow-up to #107

Issue #107 (closed by docs-only PR) asked for pagination on mmx search query because the API returns at most 10 results per call.

Investigation result

The /v1/coding_plan/search endpoint does not currently expose any pagination parameter. The canonical reference client (MiniMax-AI/MiniMax-Coding-Plan-MCP/minimax_mcp/server.py, web_search) only sends {"q": query} and the response is just { organic: [...], related_searches: [...] } — no count, page, limit, or offset is accepted or returned.

In other words, the 10-result cap is a hard limit imposed by the API, not by the CLI. The CLI cannot expose pagination flags that the server will not honor.

What is needed on the API side

To make #107 actionable, the /v1/coding_plan/search endpoint needs to accept a pagination mechanism. The simplest options would be:

1. Add a count parameter (1–N, default 10) so callers can request larger pages, and
2. Add an offset or page parameter (1-indexed or 0-indexed) so callers can paginate beyond the first page.

Both should be added to:

• MiniMax-AI/MiniMax-Coding-Plan-MCP/minimax_mcp/server.py (web_search tool)
• Any underlying API gateway that proxies the request

Once the API supports these, the CLI can be updated to expose --page and --limit flags (and the SDK's SearchSDK.query can accept the same options).

Tracking

Closing the docs gap for #107 in this repo was done in the matching PR. This issue tracks the API-side work.

Refs #107.

Start with MiniMax-AI/MiniMax-Coding-Plan-MCP/minimax_mcp/server.py and inspect the web_search tool, then trace the underlying API gateway that proxies /v1/coding_plan/search. Confirm where pagination parameters and response behavior can be implemented. Done means the API accepts a documented count and page or offset mechanism, after which the CLI and SDK can expose matching options.