Query, Search & MCP

Query mode (SQL)

The query endpoint is designed for read-only usage. Only safe query classes are allowed (for example SELECT, WITH, EXPLAIN), with timeout/limit handling and query logging.

This gives you:

• direct analysis on tables
• traceable query history
• lower risk of unintended data changes

Search mode (natural language + index)

Search indexing can be enabled per dataset. When enabled, tables are synced to search indexes and become available for natural language retrieval.

Key points:

• per-table search status
• sync/refresh mechanism
• can be combined with SQL querying

Stored queries as tool functions

Stored queries are parameterized SQL snippets exposed as reusable functions. They are useful to constrain agents to approved business operations.

Examples:

• KPI report by region and time range
• open tickets by team
• pipeline status by sales owner

MCP access

Dataset Manager supports MCP-based tool usage with dataset-scoped, header-based authentication. This lets an assistant access query, search, and stored-query tools for a specific dataset.

For tool design and rollout, see:

• Custom MCP Server
• Building MCP Tooling