BlazeSQL MCP Server

@arjshiv

About BlazeSQL MCP Server

No overview available yet

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "blaze-sql-mcp-server": {
      "command": "node",
      "args": [
        "build/index.js"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is BlazeSQL MCP Server?

BlazeSQL MCP Server is a secure-by-default MCP server and CLI for the BlazeSQL natural-language query API. It exposes a single MCP tool (blazesql_query) and also provides a direct CLI (query command) for running queries from the shell. It is designed for developers using MCP-compatible clients like Cursor, Claude Desktop, or Codex.

How to use BlazeSQL MCP Server?

Install with pnpm install, copy .env.sample to .env, and set your BLAZE_API_KEY. Build with pnpm build. Run as an MCP stdio server using node build/index.js (or node build/index.js serve). Use the CLI directly with node build/index.js query --db-id <db_id> --request "<query>". The exposed MCP tool is blazesql_query, which accepts db_id and natural_language_request parameters.

Key features of BlazeSQL MCP Server

MCP tool: blazesql_query for natural-language database queries
CLI commands: serve, query, doctor, help, version
Security defaults: HTTPS-only, bounded timeouts, redacted logging, capped output
Runtime config validation and BlazeSQL response-shape validation
Supports MCP clients: Cursor, Claude Desktop, Codex, and others
Compatible with mcporter for automated discovery and invocation

Use cases of BlazeSQL MCP Server

Query a database using natural language from an MCP client (e.g., Claude Desktop)
Run a single BlazeSQL request from the command line with query command
Check server configuration and diagnose issues with the doctor command
Integrate with CI/CD pipelines for automated database queries
Use mcporter to call the MCP tool from any project or ad-hoc script

FAQ from BlazeSQL MCP Server

What are the runtime requirements?

Node.js >=20.11.0 and pnpm >=10 are required. You also need a BlazeSQL API key.

How do I get a BlazeSQL API key?

The README instructs you to set BLAZE_API_KEY in the .env file. The key is not included in the repository; you must obtain one from BlazeSQL.

What transport does the MCP server use?

The MCP server runs as a stdio server. It is started with node build/index.js (or node build/index.js serve).

What security features are included?

HTTPS-only remote endpoints, bounded request timeouts, redacted logging (API key never printed in doctor output), and capped formatted output.

Can I use the server without an MCP client?

Yes. The CLI supports a query command that runs a single BlazeSQL request directly from the shell, with output formats including markdown, text, and json.

Frequently asked questions

What are the runtime requirements?

Node.js >=20.11.0 and pnpm >=10 are required. You also need a BlazeSQL API key.

How do I get a BlazeSQL API key?

The README instructs you to set `BLAZE_API_KEY` in the `.env` file. The key is not included in the repository; you must obtain one from BlazeSQL.

What transport does the MCP server use?

The MCP server runs as a stdio server. It is started with `node build/index.js` (or `node build/index.js serve`).

What security features are included?

HTTPS-only remote endpoints, bounded request timeouts, redacted logging (API key never printed in `doctor` output), and capped formatted output.

Can I use the server without an MCP client?

Yes. The CLI supports a `query` command that runs a single BlazeSQL request directly from the shell, with output formats including markdown, text, and json.