Most database servers stop at returning rows, which leaves the last step — putting the answer somewhere a colleague will see it — as manual work. Being able to chart a result and pin it to an existing dashboard means an ad-hoc question can become a permanent panel in the same conversation. The saved-query library serves the same purpose in reverse: the agent can reuse a query someone already got right instead of reinventing it.
BlazeSQL's endpoint. Thirteen tools split three ways: schema exploration and query execution, a library of saved queries, and dashboards you can add charts to.
- list_schemas, list_tables, describe_tables — find the shape before writing the query
- execute_sql — run it
- Saved queries: list, search, read
- Dashboards: list, search, read
- graph_sql_result and add_graph_to_dashboard — turn a result into a chart and put it somewhere people look
OAuth 2.0 with dynamic client registration. MCP is gated behind the Blaze Team Advanced subscription — the documentation states it as a prerequisite. Query results pass through BlazeSQL's servers but are documented as not stored beyond the session.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen