BlazeSQL MCP Server
The BlazeSQL MCP Server allows MCP-compatible clients to interact with BlazeSQL databases using natural language queries.
Execute Natural Language Queries: Translate natural language requests into SQL queries and execute them against a specified BlazeSQL database.
Retrieve Structured Results: Receive the agent's natural language explanation, the generated SQL query, and the query results in JSON format.
Use MCP Tool: Interact with BlazeSQL via the
blazesql_querytool by providing a database ID (db_id) and a natural language request.Secure Communication: Uses standard MCP stdio transport for seamless integration with clients like MCP Inspector and Cursor.
Robust Validation: Ensures correct usage through input parameter validation with
zodand secure API key handling.
Handles API key authentication securely via environment variables for connecting to the BlazeSQL service.
Provides integration with BlazeSQL Natural Language Query API, allowing users to query databases using natural language requests and receive SQL queries and formatted results.
Used to implement the MCP server that connects to BlazeSQL's API, enabling natural language database querying capabilities.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@BlazeSQL MCP Servershow me the top 5 customers by total purchase amount"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
BlazeSQL MCP Server
blaze-sql-server is a secure-by-default MCP server and CLI for the BlazeSQL natural-language query API.
It supports two modes:
serve: run as an MCP stdio server for Cursor, Claude Desktop, Codex, and other MCP clientsquery: execute a single BlazeSQL request directly from the shell
Highlights
MCP tool: exposes
blazesql_queryCLI commands:
serve,query,doctor,help,versionSecurity defaults: HTTPS-only remote endpoints, bounded timeouts, redacted logging, capped formatted output
Validation: runtime config validation plus BlazeSQL response-shape validation
Tooling:
pnpm, CI, automated tests, and project-levelmcporterconfig
Related MCP server: MCP MySQL Server
Requirements
Node.js
>=20.11.0pnpm>=10A BlazeSQL API key
Install
pnpm install
cp .env.sample .envSet at least:
BLAZE_API_KEY=YOUR_API_KEY_HEREOptional environment variables:
BLAZE_API_ENDPOINTBLAZE_REQUEST_TIMEOUT_MSBLAZE_MAX_RESPONSE_CHARSBLAZE_LOG_LEVELBLAZE_ALLOW_INSECURE_ENDPOINT
Build
pnpm buildRun As MCP Server
For backward compatibility, running the binary with no arguments starts the stdio server:
node build/index.jsExplicitly:
node build/index.js serveThe exposed MCP tool is:
blazesql_querydb_id: BlazeSQL database IDnatural_language_request: the prompt to send to BlazeSQL
Use With MCPorter
MCPorter can discover this server automatically via the project-level config at config/mcporter.json.
From the project root:
npx mcporter list
npx mcporter call blazesql.blazesql_query db_id:"your_db_id" natural_language_request:"show me total users"Ad hoc usage from anywhere:
npx mcporter call --stdio "node /path/to/blaze-sql-mcp-server/build/index.js" --name blazesql blazesql.blazesql_query db_id:"your_db_id" natural_language_request:"total sales last month"Run As CLI
Print help:
node build/index.js --helpRun a direct query:
node build/index.js query --db-id db_demo --request "show me total users by city"Use positional arguments:
node build/index.js query db_demo "show me total users by city"Read the request from stdin:
printf 'show me total users by city\n' | node build/index.js query db_demo --stdinAvailable output formats:
node build/index.js query db_demo "show me total users by city" --format markdown
node build/index.js query db_demo "show me total users by city" --format text
node build/index.js query db_demo "show me total users by city" --format jsonDiagnostics
Check runtime configuration:
node build/index.js doctor
node build/index.js doctor --jsondoctor is safe to run in shared terminals: it never prints the raw API key.
Validate
pnpm typecheck
pnpm test
pnpm checkMCP Client Configuration
Example stdio command:
/absolute/path/to/node /absolute/path/to/blaze-sql-mcp-server/build/index.jsBecause the binary defaults to serve, MCP clients do not need an extra subcommand.
Design Notes
The CLI shape intentionally follows the same single-purpose command pattern popularized by tools like mcporter: a predictable command surface, direct shell usage, and one obvious machine-readable mode where it matters.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/arjshiv/blaze-sql-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server