DBSQL MCP output limit

Manas2000 — Wed, 17 Jun 2026 09:28:45 GMT

Hi, Databricks Champions

I am using SQL MCP server. I was able to connect to MCP and run my sql queries. However as my query out goes above 32,768 it gets truncated and I am not able to get the complete output.

I can only pass warehouse_id in "_meta" parameters while making connection. There is no way for me to configure row_limit.

poll → state='SUCCEEDED'

Final state: SUCCEEDED

── MANIFEST (excl. schema) ──
{
"format": "PROTOBUF_ARRAY",
"total_chunk_count": 1,
"chunks": [
{
"chunk_index": 0,
"row_offset": 0,
"row_count": 32768,
"byte_count": 1860920
}
],
"total_row_count": 32768,
"total_byte_count": 1860920,
"truncated": true
}

── RESULT keys ──
['chunk_index', 'row_offset', 'row_count', 'data_typed_array']

It's literally giving me a single chunk only (with truncated = True) and there is no way for me to get the further data because chunks are not given to me.

Has anyone encountered this limitation with the SQL MCP Server? Is there a supported way to:

Increase the result row limit?
Configure pagination/chunking?
Retrieve the rows beyond the 32,768-row cutoff?

Any guidance would be greatly appreciated.

Thanks

Re: DBSQL MCP output limit

frankieseabrook — Thu, 18 Jun 2026 22:09:17 GMT

HI @Manas2000 ,

This appears to be a Databricks SQL MCP limitation, not a Databricks SQL warehouse limitation.

A hacky workaround might be to manually paginate in SQL, e.g., with `ROW_NUMBER()` or `LIMIT/OFFSET`, and run separate MCP calls for each page.

But candidly for large result extraction, MCP is the wrong tool. You could use the Databricks Statement Execution API directly with chunking or `EXTERNAL_LINKS`.

Hope that helps.

topic DBSQL MCP output limit in Generative AI

DBSQL MCP output limit

Re: DBSQL MCP output limit