LabscoMCP early access ↗
firebolt-dbMCP SERVER · OFFICIAL PROJECT

Firebolt

Query a Firebolt data warehouse and read Firebolt's own documentation in the same session.

by firebolt-db ↗Relational SQL Databases✓ Official

LABSCO SUMMARY

It reads the documentation before it writes your SQL.

By default the connect tool will not proceed until the model has fetched the documentation overview, which grounds it in Firebolt's dialect instead of generic SQL — turn that off with --skip-docs-proof when the extra tokens aren't worth it. One client caveat: the server leans on MCP resources, so Cursor needs FIREBOLT_MCP_DISABLE_RESOURCES=true or it will not work at all.

What it is

Firebolt's MCP server: a Go binary that connects an assistant to a Firebolt engine and database, and to Firebolt's SQL reference and documentation.

What you get

  • firebolt_connect — attach to an engine and a database
  • firebolt_query — execute SQL against Firebolt
  • firebolt_docs_overview and firebolt_docs_search — the documentation, SQL reference and function lists, searchable from the conversation
  • Resources the model can reference directly: documentation articles and the lists of accounts, databases and engines
  • A Firebolt Expert prompt that puts the model in the right frame before it writes SQL

Requirements

Either a Firebolt service account with a client id and secret, in FIREBOLT_MCP_CLIENT_ID and FIREBOLT_MCP_CLIENT_SECRET, or a Firebolt Core instance URL in FIREBOLT_MCP_CORE_URL. Run ghcr.io/firebolt-db/mcp-server:0.6.0 under Docker or download the binary from Releases. STDIO is the default transport; set --transport sse for Server-Sent Events.

Setup effort

One command plus credentials — docker run --rm --network host -e FIREBOLT_MCP_CLIENT_ID=<YOUR_FIREBOLT_MCP_CLIENT_ID> -e FIREBOLT_MCP_CLIENT_SECRET=<YOUR_FIREBOLT_MCP_CLIENT_SECRET> ghcr.io/firebolt-db/mcp-server:0.6.0