Oversized MCP result: Cline cache URI vs Sume 256 KiB limit
Cline caches oversized MCP output behind a cline://cache URI. Sume instead refuses at 256 KiB with mcp_output_too_large. Re-read narrower; never resubmit.

They are two different mechanisms. Cline SDK v0.0.89 keeps an oversized MCP result in a per-session cache and hands the model a preview plus a cline://cache/... URI. Sume's hosted MCP server describes no such cache: a result over 256 KiB comes back as an explicit mcp_output_too_large error, and the fix is a narrower or paginated read, never a resubmitted create.
Cline facts are from its releases page; Sume facts from MCP and the server source, read 2026-10-01.
What does Cline do with an oversized MCP result?
The v0.0.89 note says oversized MCP and Composio results are cached in a per-session in-memory cache. The model receives a bounded preview and a cline://cache/... URI that read_files can page through by line range. Entries expire after five model iterations without a read, the cache is capped at 16 MiB per session, and the original output stays in history and tool events.
What does Sume do with an oversized result?
The hosted server defines one cap, MCP_OUTPUT_MAX_BYTES = 256 * 1024. Above it the tool returns a JSON result with code mcp_output_too_large, the max_bytes value, and this message: use a narrower or paginated read; this is an output limit, not a job failure; never resubmit a paid create.
| Cline v0.0.89 | Sume hosted MCP | |
|---|---|---|
| Trigger | Result judged oversized | Result over 256 KiB |
| What the model gets | Bounded preview plus a cline://cache/... URI | mcp_output_too_large with max_bytes |
| Full output | Cached per session, up to 16 MiB | Not returned |
| Next step | Page with read_files by line range | Narrower or paginated read |
Which one applies when Cline calls Sume?
Both can be in play, in order. Sume's cap applies first, on the server, and the Cline cache only sees what Sume returned. So an over-cap Sume result reaches Cline as the small error above, and there is no full output to page through. Point Cline at the hosted URL, https://mcp.sume.com/mcp, as the docs describe for remote MCP clients; see also Cline setup for Sume.
What should I re-read after the error?
Ask for less: a smaller page, fewer ids, or a single job. For job output, read by id with jobs_status or jobs_result instead of listing everything. The error is not a failed generation, so the paid job that produced the data is untouched. Resubmitting the create would run, and bill, a second job. The tools and gates page lists the read tools.
Sources
Related posts
More in Integrations
- Runway MCP workflows vs Sume hosted MCP tool chains
Runway MCP can now list, open and run saved workflows from chat. Sume's hosted MCP exposes single tools you chain with jobs_wait and an idempotency_key.
- Shopify collection.products trigger: one Sume job per product added
Shopify Events' collection.products trigger fires when a product joins or leaves a collection. Key one Sume image job on collection and product ids.
- Shopify Events fields_changed: only added should start a Sume job
Shopify Events' fields_changed is now an object with added, updated and removed. Start a paid Sume job from added only, and key it so replays are safe.
- Shopify Events query_filter: ACTIVE products only for Sume runs
Shopify Events' query_filter can limit deliveries to ACTIVE products. Filter at Shopify so draft products never reach a Sume submit or a bulk queue.
Written by Sume