mcpField
B
BlazeSQL MCP Server

BlazeSQL MCP Server

Local
github.com/arjshivDatabases0Updated 31w ago

About BlazeSQL MCP Server

BlazeSQL MCP Server is a Node.js MCP server and CLI for sending natural-language queries to the BlazeSQL API. It offers a stdio tool for MCP clients as well as direct shell queries, with validation and security-oriented defaults.

Key features

  1. 01MCP tool for BlazeSQL queries
  2. 02Direct shell query command
  3. 03Markdown, text, and JSON output
  4. 04Configuration diagnostics
  5. 05Validated responses and bounded output

Use cases

  1. 01Query a BlazeSQL database from an MCP client
  2. 02Run a one-off database query from the shell
  3. 03Check runtime configuration without exposing the API key

MCP support

It exposes the `blazesql_query` tool, accepting a BlazeSQL database ID and a natural-language request. MCP clients can run it over stdio.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

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 clients
  • query: execute a single BlazeSQL request directly from the shell

Highlights

  • MCP tool: exposes blazesql_query
  • CLI commands: serve, query, doctor, help, version
  • Security 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-level mcporter config

Requirements

  • Node.js >=20.11.0
  • pnpm >=10
  • A BlazeSQL API key

Install

pnpm install
cp .env.sample .env

Set at least:

BLAZE_API_KEY=YOUR_API_KEY_HERE

Optional environment variables:

  • BLAZE_API_ENDPOINT
  • BLAZE_REQUEST_TIMEOUT_MS
  • BLAZE_MAX_RESPONSE_CHARS
  • BLAZE_LOG_LEVEL
  • BLAZE_ALLOW_INSECURE_ENDPOINT

Build

pnpm build

Run As MCP Server

For backward compatibility, running the binary with no arguments starts the stdio server:

node build/index.js

Explicitly:

node build/index.js serve

The exposed MCP tool is:

  • blazesql_query
  • db_id: BlazeSQL database ID
  • natural_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 --help

Run 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 --stdin

Available 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 json

Diagnostics

Check runtime configuration:

node build/index.js doctor
node build/index.js doctor --json

doctor is safe to run in shared terminals: it never prints the raw API key.

Validate

pnpm typecheck
pnpm test
pnpm check

MCP Client Configuration

Example stdio command:

/absolute/path/to/node /absolute/path/to/blaze-sql-mcp-server/build/index.js

Because 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.