Supported Databases
QueryWeaver works with the following SQL databases:Resources
- 🔗 QueryWeaver Website
- 💻 GitHub Repository
- 🐳 Docker Hub
- 📖 Swagger API Docs
- ☁️ Try Free on FalkorDB Cloud
Quick Start
Docker
The fastest way to get started is with Docker:Note: You will need to connect a supported database (PostgreSQL, MySQL, or Snowflake) through the UI or via environment variables before running queries.Then open http://localhost:5000 in your browser.
Using an .env File (Recommended)
For a configured deployment, copy the example environment file and pass it to Docker:
AI/LLM Configuration
QueryWeaver supports multiple AI providers. Set one provider-specific environment variable and QueryWeaver auto-detects which provider to use. For Ollama, setOLLAMA_MODEL to your local model name; for all other providers, set the corresponding API key.
Priority order: Ollama > OpenAI > Gemini > Anthropic > Cohere > Azure
Example using OpenAI:
REST API
QueryWeaver exposes a REST API for managing database schemas (graphs) and running Text2SQL queries. All endpoints require a bearer token for authentication.Core Endpoints
Authentication
Add anAuthorization header with your API token:
/tokens routes. For a local Docker deployment, any token you create through the UI at http://localhost:5000 will work.
Examples
List graphs:MCP Server Support
QueryWeaver includes built-in support for the Model Context Protocol (MCP), exposing Text2SQL operations as MCP tools:list_databasesconnect_databasedatabase_schemaquery_database
mcp.json file:
claude_desktop_config.json), QueryWeaver’s HTTP MCP surface can be referenced using:
Use Cases
- Natural Language Database Queries: Ask questions in plain English and get SQL answers against PostgreSQL, MySQL, or Snowflake databases
- Snowflake Analytics: Query your Snowflake data warehouse using plain English, no SQL expertise required
- Multi-database Support: Connect and query across PostgreSQL, MySQL, and Snowflake from a single interface
- Schema Exploration: Browse and understand database schemas through conversation
- Data Analysis: Run ad-hoc queries without knowing SQL syntax
- API Integration: Embed Text2SQL capabilities in your own applications
Related Tools
- FalkorDB MCP Server: Enable AI assistants to interact with FalkorDB using MCP
- GraphRAG-SDK: Build intelligent GraphRAG applications with FalkorDB and LLMs
Frequently Asked Questions
What is QueryWeaver?
What is QueryWeaver?
QueryWeaver is an open-source Text2SQL tool that converts plain-English questions into SQL queries using graph-powered schema understanding. It uses FalkorDB to store and reason over database schema relationships as a graph, enabling more accurate SQL generation.
Which databases does QueryWeaver support?
Which databases does QueryWeaver support?
QueryWeaver supports PostgreSQL, MySQL, and Snowflake. Connect your database through the web UI or via environment variables, and QueryWeaver will introspect the schema to enable accurate Text2SQL generation.
Which AI providers does QueryWeaver support?
Which AI providers does QueryWeaver support?
QueryWeaver supports Ollama (local models), OpenAI, Google Gemini, Anthropic, Cohere, and Azure OpenAI. Set the appropriate environment variable and QueryWeaver auto-detects the provider. Priority order: Ollama > OpenAI > Gemini > Anthropic > Cohere > Azure.
Can I use QueryWeaver with MCP-compatible AI assistants?
Can I use QueryWeaver with MCP-compatible AI assistants?
Yes. QueryWeaver includes built-in MCP server support, exposing tools like
list_databases, connect_database, database_schema, and query_database. Configure your MCP client (Claude Desktop, VS Code Copilot) to connect to http://127.0.0.1:5000/mcp.How do I get started quickly?
How do I get started quickly?
Run
docker run -p 5000:5000 -it falkordb/queryweaver and open http://localhost:5000 in your browser. Set an LLM provider API key (e.g., OPENAI_API_KEY) as an environment variable for AI-powered SQL generation.Does QueryWeaver have a REST API?
Does QueryWeaver have a REST API?
Yes. QueryWeaver exposes REST endpoints for managing graphs and running Text2SQL queries. Key endpoints include
GET /graphs to list databases, POST /graphs/{graph_id} to run queries, and all require Bearer token authentication.