docs: document the searchExplorations MCP tool

[igorlukanin]

Summary

• Documents the searchExplorations MCP tool, which searches saved queries — explorations and workbook tabs alike — by name and description and returns each one's sqlQuery, ready to pass to runQuery.
• Adds it to the "Query and discovery" table and updates the tool count.

Test plan

• Table renders with the new row; surrounding guidance reads correctly
• CI must pass

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
cubed3	🟢 Ready	View Preview	Aug 13, 2026, 11:39 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[claude]

Claude finished @igorlukanin's task in 1m 18s —— View job

---

Review complete — docs-only change, looks good to merge. 0 high, 0 medium, 3 low (2 inline nits + 1 verification ask)

Full review

Todos

• Gather context (read diff)
• Verify tool count and table contents in the doc
• Check terminology against docs-mintlify/CLAUDE.md
• Check for existing Claude review threads (none — nothing to resolve or dedupe against)
• Post review

What's correct

• Tool count is accurate. I counted the tool rows across all five tables in mcp-server.mdx — listDeployments, chat, loadQueryResults (3), Query and discovery (3), Dashboard authoring (5), Data model editing (8), pre-aggregations (2) = 21, matching the updated line 232.
• Terminology matches the style guide. "explorations" and "workbook tabs" line up with the product taxonomy in docs-mintlify/CLAUDE.md (Workbook → Tab, Explore → Explorations). No "Cube Cloud" or other legacy naming introduced.
• Access annotation is consistent. Read-only matches the other query/discovery rows, and the destructive-tools paragraph at lines 240–244 still says "four destructive ones" — correctly unaffected by this addition.
• Table syntax is valid (3 columns, matching the header), and the change lives in the active /docs-mintlify site, not the deprecated /docs.

Findings (all low severity, posted inline)

#	Location	Note
1	docs-mintlify/docs/integrations/mcp-server.mdx:263	No link reference for "explorations" — other rows link [ref-sql-api] / [ref-workbooks] / [ref-dashboards]; /docs/explore-analyze/explore#saving-explorations exists and would fit. Also: the row is listed after runQuery while the prose says to call it first.
2	docs-mintlify/docs/integrations/mcp-server.mdx:268-271	The new guidance paragraph is four lines and slightly editorial, next to the one-sentence searchDataModel/runQuery guidance above it. docs-mintlify/CLAUDE.md asks for the shortest version that answers "how do I use this?" — suggested a tighter rewrite.
3	—	Two factual claims can't be verified from this repo (the MCP server implementation isn't here): that the returned field is literally sqlQuery, and that results are access-scoped per user. Both are load-bearing for a reader; worth a confirmation from the implementation.

Not applicable

Security, performance, and test-coverage checks don't apply — this is a 7-line documentation change with no code, no build, and no test surface. I did not run the Mintlify dev server (no dependency install in this environment); the table and MDX are syntactically plain and render-safe by inspection.

• [`igor/cub-3760-document-searchexplorations-mcp-tool`](https://github.com/cube-js/cube/tree/igor/cub-3760-document-searchexplorations-mcp-tool)

[claude]

Claude finished @igorlukanin's task in 1m 11s —— View job

---

Re-review of the updated diff — both prior nits addressed, docs-only, good to merge. 0 high, 0 medium, 1 low (non-blocking)

Full review

Todos

• Gather context (read diff since last review)
• Verify tool count, link reference, and anchor target
• Check existing Claude review threads (both already resolved — nothing to resolve or dedupe)
• Post review

What changed since my last review

Both of my earlier inline nits were addressed, and their threads are already resolved:

1. Link reference added. [ref-explorations]: /docs/explore-analyze/explore#saving-explorations is defined at line 442 alongside the other refs and used in the new table row at line 261. I verified the target: docs-mintlify/docs/explore-analyze/explore.mdx exists, is registered in docs.json, and contains ## Saving explorations (line 50) — so the #saving-explorations anchor resolves.
2. Ordering fixed. searchExplorations now sits at the top of the Query and discovery table (line 261), ahead of searchDataModel and runQuery, matching the "call it first" guidance in the prose below.
3. Concision improved. The editorializing ("the numbers your team already trusts") is gone. The paragraph is still four lines, but the fourth line is now the substantive sqlQuery: null caveat rather than filler, and the Otherwise call searchDataModel… transition reads cleanly.

Verification

• Tool count is correct. Counted the tool rows across all five tables: Deployments and chat (3) + Query and discovery (3) + Dashboard authoring (5) + Data model editing (8) + pre-aggregations (2) = 21, matching line 232.
• Destructive-tools paragraph unaffected. Lines 240–244 still name four destructive tools; searchExplorations is Read-only, consistent with the other rows in its table.
• Terminology matches the style guide. "explorations" and "workbook tabs" line up with the taxonomy in docs-mintlify/CLAUDE.md (Explore → Explorations, Workbook → Tab). No legacy "Cube Cloud" naming introduced.
• MDX is valid — 3 columns matching the header, link reference defined exactly once, change is in the active /docs-mintlify site rather than the deprecated /docs.

Low (non-blocking, no inline comment posted)

Minor tension between the table row and the prose: line 261 says the tool "Returns each one's sqlQuery, ready to pass to runQuery" with no caveat, while line 268 says a saved query with no runnable SQL comes back with sqlQuery set to null. The prose resolves it seven lines later, so a reader isn't left wrong — but if you want the row to stand alone, "Returns each one's sqlQuery, where available" would close the gap. Purely optional.

Still unverified from this repo

The MCP server implementation isn't in this repo, so I still can't confirm two load-bearing claims: that the returned field is literally named sqlQuery (including the null behavior now documented), and that results are scoped to the explorations the caller can access. Both read as intentional and specific, so I'd assume they came from the implementation — flagging only so the claim isn't unverified by silence.

Not applicable

Security, performance, and test-coverage checks don't apply — this is a documentation-only change with no code, no build surface, and no tests. I did not run the Mintlify dev server (no dependency install in this environment); the Mintlify preview build linked above is green.

• [`igor/cub-3760-document-searchexplorations-mcp-tool`](https://github.com/cube-js/cube/tree/igor/cub-3760-document-searchexplorations-mcp-tool)

[claude]

Re-review of the synchronized diff — docs-only, all prior nits addressed, good to merge. 0 high, 0 medium, 1 low (non-blocking)

Full review

Todos

• Gather context (read git diff origin/master...HEAD)
• Verify tool count against every table
• Verify [ref-explorations] definition and anchor target
• Check existing Claude review threads (both already resolved — nothing to resolve or dedupe)
• Post review

Verification

• Tool count is correct. Counted the tool rows across all five tables in mcp-server.mdx: Deployments and chat (3) + Query and discovery (3) + Dashboard authoring (8) + Data model editing (8) + Pre-aggregations (2) = 24, matching the updated line 232. Note this differs from the 21 I counted on the previous head — the Dashboard authoring table has grown since, so the diff's 23 → 24 bump lands on the right total for the current file.
• Link reference resolves. [ref-explorations]: /docs/explore-analyze/explore#saving-explorations is defined at line 457 alongside the other refs and used once, at line 262. The target docs-mintlify/docs/explore-analyze/explore.mdx exists, is registered in docs.json:60, and contains ## Saving explorations (line 50) — so the anchor resolves.
• Ordering matches the prose. searchExplorations sits at the top of the Query and discovery table (line 262), ahead of searchDataModel and runQuery, consistent with the "call it first" guidance at line 266 and the Otherwise call searchDataModel… transition at line 271.
• Destructive-tools paragraph unaffected. Lines 240–245 name six destructive tools (updateReport, deleteReport, updateDashboard, publishDashboard, writeDataModelFile, deleteDataModelFile) — count is accurate, and searchExplorations is Read-only, consistent with the rest of its table.
• Terminology matches the style guide. "explorations" and "workbook tabs" line up with the taxonomy in docs-mintlify/CLAUDE.md (Explore → Explorations, Workbook → Tab). No legacy "Cube Cloud" naming introduced.
• MDX is valid — 3 columns matching the header, link reference defined exactly once, change is in the active /docs-mintlify site rather than the deprecated /docs.
• Prior threads. Both of my earlier inline nits (missing link reference + row ordering; paragraph concision) are addressed in a671eef and their threads are already resolved. Nothing to resolve or re-post.

Low (non-blocking, no inline comment posted)

Same minor tension I flagged last round: line 262 says the tool "Returns each one's sqlQuery, ready to pass to runQuery" with no qualifier, while line 269 says a saved query with no runnable SQL comes back with sqlQuery set to null. The prose resolves it seven lines later, so no reader ends up wrong — but "Returns each one's sqlQuery, where available" would let the row stand alone. Purely optional; not re-posting inline since it's unchanged from the previous review.

Confirmed claims

The two claims I couldn't verify from this repo (the field is literally named sqlQuery; results are access-scoped per user) were confirmed by @igorlukanin against the server implementation — CompactExploration in mcp-tools/data-tools.ts, with search running through the RBAC-filtered report query. Recording that here so the audit trail is closed.

Not applicable

Security, performance, and test-coverage checks don't apply — documentation-only change with no code, no build surface, and no tests. I did not run the Mintlify dev server (no dependency install in this environment); the linked Mintlify preview build is green.

View job run • igor/cub-3760-document-searchexplorations-mcp-tool

[claude]

Re-review of the synchronized diff — docs-only, every prior nit now closed. 0 high, 0 medium, 0 low — good to merge

Full review

Todos

• Gather context (git diff origin/master...HEAD, commit log)
• Verify tool count against every table
• Verify [ref-explorations] definition and anchor target
• Check existing review threads (both prior Claude threads already resolved)
• Post review

What changed since the last review

094c8f9 addresses the one low finding I left open across the previous two rounds: the table row now reads "Returns each one's sqlQuery, where available, ready to pass to runQuery", so the row no longer overstates availability relative to the sqlQuery set to null caveat in the prose below it. The row stands alone correctly now; nothing left to flag.

Verification

• Tool count is correct. Counted every tool row in mcp-server.mdx: Deployments and chat (3, lines 251–253) + Query and discovery (3, lines 262–264) + Dashboard authoring (8, lines 281–288) + Data model editing (8, lines 309–316) + Pre-aggregations (2, lines 360–361) = 24, matching the updated line 232.
• Link reference resolves. [ref-explorations]: /docs/explore-analyze/explore#saving-explorations is defined once at line 457 alongside the other refs and used once at line 262. Target docs-mintlify/docs/explore-analyze/explore.mdx contains ## Saving explorations (line 50), so the anchor resolves.
• Ordering matches the prose. searchExplorations sits at the top of the Query and discovery table, ahead of searchDataModel and runQuery, consistent with the "call it first" guidance and the Otherwise call searchDataModel… transition.
• Destructive-tools paragraph unaffected. Still names six destructive tools; searchExplorations is Read-only, consistent with the rest of its table.
• Terminology matches the style guide. "explorations" and "workbook tabs" line up with the taxonomy in docs-mintlify/CLAUDE.md (Explore → Explorations, Workbook → Tab). No legacy "Cube Cloud" naming.
• MDX is valid — 3 columns matching the header, and the change is in the active /docs-mintlify site rather than the deprecated /docs.

Threads

Both earlier inline threads (missing link reference + row ordering; paragraph concision) are resolved and outdated. Nothing to resolve or re-post; no new inline comments this round.

Confirmed claims

The two claims not verifiable from this repo — the field is literally named sqlQuery, and results are access-scoped per user — were confirmed by @igorlukanin against the server implementation (CompactExploration in mcp-tools/data-tools.ts, search running through the RBAC-filtered report query). Audit trail closed.

Not applicable

Security, performance, and test-coverage checks don't apply — documentation-only change with no code, no build surface, and no tests. I did not run the Mintlify dev server (no dependency install in this environment); the linked Mintlify preview build is green.

View job run • igor/cub-3760-document-searchexplorations-mcp-tool

[claude]

Claude finished @igorlukanin's task in 50s —— View job

---

Re-review of the synchronized diff — docs-only, nothing outstanding. 0 high, 0 medium, 0 low — good to merge

Full review

Todos

• Gather context (git diff origin/master...HEAD, commit log)
• Verify tool count against every table
• Verify [ref-explorations] definition and anchor target
• Check existing review threads (both prior Claude threads already resolved and outdated)
• Post review

What changed

The branch is now three commits (24dd632, d18b088, f330617) and the diff is a clean +10/−3 in docs-mintlify/docs/integrations/mcp-server.mdx. Line numbers shifted since my earlier rounds (the table now sits at 239–243), but the content is the same one I signed off on: the where available qualifier is in the row, the link reference is defined, and the row leads the table.

Verification

• Tool count is correct. Counted every tool row in the file: Deployments and chat (3, lines 230–232) + Query and discovery (3, lines 241–243) + Dashboard authoring (8, lines 260–267) + Data model editing (8, lines 288–295) + Pre-aggregations (2, lines 339–340) = 24, matching the updated line 211.
• Link reference resolves. [ref-explorations]: /docs/explore-analyze/explore#saving-explorations is defined once at line 436 alongside the other refs, used once at line 241. Target docs-mintlify/docs/explore-analyze/explore.mdx contains ## Saving explorations (line 50) and is registered in docs.json:60, so the anchor resolves.
• Row stands alone. Line 241 reads "Returns each one's sqlQuery, where available, ready to pass to runQuery", consistent with the sqlQuery set to null caveat at line 248. No tension left between the row and the prose.
• Ordering matches the prose. searchExplorations leads the table, ahead of searchDataModel and runQuery, matching the "call it first" guidance at line 245 and the Otherwise call searchDataModel… transition at line 250.
• Destructive-tools paragraph unaffected. Lines 219–224 still name six destructive tools; searchExplorations is Read-only, consistent with the rest of its table.
• Terminology matches the style guide. "explorations" and "workbook tabs" line up with the taxonomy in docs-mintlify/CLAUDE.md (Explore → Explorations, Workbook → Tab). No legacy "Cube Cloud" naming.
• MDX is valid — 3 columns matching the header, reference defined exactly once, change is in the active /docs-mintlify site rather than the deprecated /docs.

Threads

Both earlier inline threads (missing link reference + row ordering; paragraph concision) are resolved and outdated. Nothing to resolve or re-post; no new inline comments this round.

Confirmed claims

The two claims not verifiable from this repo — the field is literally named sqlQuery, and results are access-scoped per user — were confirmed by @igorlukanin against the server implementation (CompactExploration in mcp-tools/data-tools.ts, search running through the RBAC-filtered report query). Audit trail closed.

Not applicable

Security, performance, and test-coverage checks don't apply — documentation-only change with no code, no build surface, and no tests. I did not run the Mintlify dev server (no dependency install in this environment); the linked Mintlify preview build is green.

• [`igor/cub-3760-document-searchexplorations-mcp-tool`](https://github.com/cube-js/cube/tree/igor/cub-3760-document-searchexplorations-mcp-tool)

[claude]

Claude finished @igorlukanin's task in 33s —— View job

---

Re-review of the synchronized diff — docs-only, unchanged content since last sign-off. 0 high, 0 medium, 0 low — good to merge

Full review

Todos

• Gather context (git diff origin/master...HEAD, commit log)
• Verify tool count against every table
• Verify [ref-explorations] definition and anchor target
• Check existing review threads (both prior Claude threads resolved and outdated)
• Post review

What changed

Nothing substantive. The branch is the same three commits (6421b0e, 29d63e7, 98a4a44) and the diff is a clean +10/−3 in docs-mintlify/docs/integrations/mcp-server.mdx — identical in content to the version I signed off on last round. Line numbers are stable at 241–243 for the table and 245–250 for the prose.

Verification

• Tool count is correct. Counted every tool row in the file: Deployments and chat (3, lines 230–232) + Query and discovery (3, lines 241–243) + Dashboard authoring (8, lines 260–267) + Data model editing (8, lines 288–295) + Pre-aggregations (2, lines 339–340) = 24, matching the updated line 211.
• Link reference resolves. [ref-explorations]: /docs/explore-analyze/explore#saving-explorations is defined once at line 436 alongside the other refs, used once at line 241. Target docs-mintlify/docs/explore-analyze/explore.mdx contains ## Saving explorations (line 50), so the anchor resolves.
• Row stands alone. Line 241 reads "Returns each one's sqlQuery, where available, ready to pass to runQuery", consistent with the sqlQuery set to null caveat in the prose. No tension between row and prose.
• Ordering matches the prose. searchExplorations leads the table, ahead of searchDataModel and runQuery, matching the "call it first" guidance and the Otherwise call searchDataModel… transition.
• Destructive-tools paragraph unaffected. searchExplorations is Read-only, consistent with the rest of its table; the destructive-tools list is untouched by this diff.
• Terminology matches the style guide. "explorations" and "workbook tabs" line up with the taxonomy in docs-mintlify/CLAUDE.md (Explore → Explorations, Workbook → Tab). No legacy "Cube Cloud" naming.
• MDX is valid — 3 columns matching the header, reference defined exactly once, change is in the active /docs-mintlify site rather than the deprecated /docs.

Threads

Both earlier inline threads (missing link reference + row ordering; paragraph concision) are resolved and outdated. Nothing to resolve or re-post; no new inline comments this round.

Confirmed claims

The two claims not verifiable from this repo — the field is literally named sqlQuery, and results are access-scoped per user — were confirmed by @igorlukanin against the server implementation (CompactExploration in mcp-tools/data-tools.ts, search running through the RBAC-filtered report query). Audit trail closed.

Not applicable

Security, performance, and test-coverage checks don't apply — documentation-only change with no code, no build surface, and no tests. I did not run the Mintlify dev server (no dependency install in this environment); the linked Mintlify preview build is green.

• [`igor/cub-3760-document-searchexplorations-mcp-tool`](https://github.com/cube-js/cube/tree/igor/cub-3760-document-searchexplorations-mcp-tool)