mcp

This MCP server from Firebolt provides a Model Context Protocol implementation that connects your LLM to a Firebolt data warehouse. It enables LLM-powered agents to autonomously query Firebolt databases, access SQL references and documentation, and operate across different engines or workspaces via a single MCP interface. With the Firebolt MCP server running in Docker, you can connect to LLM environments and expose Firebolt resources to your agents, including authentication via service accounts or Core URLs. The server focuses on SQL query execution, provides access to Firebolt docs and function references, and supports multiple deployment scenarios through a Docker image or native binaries.

To use it, configure an MCP client (e.g., VS Code Copilot integration, Claude Desktop, Cursor, or other MCP-compatible clients) to point at this server. Provide credentials as environment variables (FIREBOLT_MCP_CLIENT_ID and FIREBOLT_MCP_CLIENT_SECRET) when launching the container, or switch to the Core URL approach if you are using Firebolt Core. The MCP client will communicate with Firebolt through the MCP interface, allowing your LLM to issue queries, retrieve results, and navigate Firebolt documentation via the integrated MCP resources.

Prerequisites:

• Docker installed on the host (recommended for quick setup)
• Access credentials for a Firebolt service account (client ID and client secret) or a Firebolt Core URL

Option A: Install and run with Docker

1. Authenticate with your credentials and run the container:

docker run \
  --rm \
  --network host \
  -e FIREBOLT_MCP_CLIENT_ID=your-client-id \
  -e FIREBOLT_MCP_CLIENT_SECRET=your-client-secret \
  ghcr.io/firebolt-db/mcp-server:latest

2. When prompted, supply your Firebolt client ID/secret via environment variables or bind them directly in the command above. The MCP server will start and listen for MCP clients.

Option B: Run as a binary (if you prefer)

1. Download the binary for your OS from the releases page (e.g., https://github.com/firebolt-db/mcp-server/releases/tag/v0.6.0).
2. Run the server with your credentials:

./firebolt-mcp-server \
  --client-id your-client-id \
  --client-secret your-client-secret

3. Alternatively, provide a Core URL instead of service account credentials if using Firebolt Core.

Prerequisites recap:

• Docker or binary executable for your platform
• Firebolt service account credentials or Core URL
• Network access to Firebolt services

Environment variables: FIREBOLT_MCP_CLIENT_ID, FIREBOLT_MCP_CLIENT_SECRET for service accounts. If using Firebolt Core, you can provide FIREBOLT_MCP_CORE_URL instead. When using Docker, ensure --network host is used or adjust networking to reach the Firebolt services. The configuration above uses the latest image tag; you can pin to a specific version (e.g., ghcr.io/firebolt-db/mcp-server:0.6.0) if stability is required. If you deploy in environments that restrict networking, you may need to expose ports and configure reverse proxies accordingly. Some MCP clients may require explicit JSON config snippets like mcpServers.firebolt.command and mcpServers.firebolt.args; adapt the provided example to your client’s schema.