Mcp Server

What is Mcp Server?

Mcp Server is a Model Context Protocol implementation that connects your LLM to Firebolt Data Warehouse. It integrates AI assistants directly with Firebolt databases, enabling autonomous query execution and documentation access.

How to use Mcp Server?

Mcp Server can be run via Docker or downloaded as a standalone Go binary. Configure it with a Firebolt service account (client ID and secret) or a Firebolt Core instance URL. Connect from LLM clients such as Claude Desktop, VS Code (Copilot Chat), Cursor, or any MCP-compatible client using JSON configuration.

Key features of Mcp Server

• LLM integration with Firebolt Data Warehouse
• SQL query execution against Firebolt databases
• Access to comprehensive Firebolt documentation
• Seamless authentication with Firebolt service accounts
• Supports both Firebolt Cloud and Firebolt Core
• Multi-platform support: runs anywhere Go binaries are supported, plus official Docker image

Use cases of Mcp Server

• Connect AI assistants directly to your data warehouse for autonomous querying
• Enable AI agents to generate insights from Firebolt databases
• Provide LLMs with deep knowledge of Firebolt SQL, features, and documentation
• Automate data analysis through natural language requests

FAQ from Mcp Server

What authentication methods does Mcp Server support?

Authentication is done via Firebolt service account credentials (client ID and client secret) or by providing a Firebolt Core instance URL.

Which transport mechanisms does Mcp Server support?

By default, Mcp Server uses STDIO transport. SSE (Server-Sent Events) is also supported by setting the --transport flag or FIREBOLT_MCP_TRANSPORT environment variable to sse.

Does Mcp Server work in Cursor?

Mcp Server requires Cursor to set the FIREBOLT_MCP_DISABLE_RESOURCES=true environment variable because Cursor does not support MCP resources. Dedicated one-click install buttons are provided for both Firebolt Cloud and Firebolt Core.

What tools, resources, and prompts does Mcp Server provide?

It provides tools for documentation overview (firebolt_docs_overview), connecting to Firebolt engines (firebolt_connect), executing SQL queries (firebolt_query), and searching documentation (firebolt_docs_search). Resources include documentation articles and lists of accounts, databases, and engines. A prompt named "Firebolt Expert" is also available.

Can I require the LLM to read documentation before connecting?

Yes, by default the firebolt_connect tool requires the LLM to present a read proof of Firebolt documentation. This can be disabled by setting --skip-docs-proof to false.