What is MCP?
MCP (Model Context Protocol) is an open standard that lets AI tools connect to external data sources. BlazeSQL provides an MCP server that any compatible client can use to query your databases with natural language.
Compatible Clients
BlazeSQL's generic MCP endpoint works with third-party clients that support the MCP protocol, including:
Claude Code — Anthropic's CLI coding agent
Cursor — AI-powered code editor
Windsurf — AI development environment
Cline — AI coding assistant for VS Code
Any MCP-compatible tool — The protocol is open, so new clients are being added regularly
Note: If you're using Claude (claude.ai or Claude Desktop), see Using BlazeSQL with Claude. If you're using ChatGPT, see Using BlazeSQL with ChatGPT.
Server URL
Use the following endpoint when configuring your MCP client:
https://mcp.blazesql.com/mcp
This endpoint supports both Streamable HTTP and SSE transports.
Setup Guide
A Blaze Team Advanced subscription
A BlazeSQL account with at least one connected database
An MCP-compatible client application
Step 1: Add BlazeSQL to Your MCP Client
In your MCP client's settings, add a new server connection with the URL:
https://mcp.blazesql.com/mcp
The exact steps vary by client — check your client's documentation for how to add an MCP server.
Step 2: Authenticate
When you first connect, you'll be redirected to sign in with your BlazeSQL account. After signing in, select the database you want to query and authorize the connection.
Step 3: Start Querying
Once connected, your MCP client can use the blazesql_query tool. Just ask questions about your data in natural language:
"Show me the top 10 customers by revenue"
"How many new users signed up each week this year?"
"What's the average response time by support agent?"
Configuration Examples
Claude Code
Add BlazeSQL as an MCP server using the Claude Code CLI:
claude mcp add blazesql --transport http https://mcp.blazesql.com/mcp
Cursor
Add BlazeSQL as an MCP server in your Cursor settings under the MCP section, using the URL https://mcp.blazesql.com/mcp.
Troubleshooting
Authentication issues
If the OAuth sign-in window doesn't appear, check that your MCP client supports OAuth 2.0 authentication. Some clients may require you to manually configure the authorization URL.
Connection timeout
Ensure your MCP client is configured to use the correct URL with the /mcp path. The base domain alone won't work.
Need help?
Reach out via the chat widget on blazesql.com or email support@blazesql.com.