An MCP server for Text2SQL: transforms natural language into SQL using graph schema understanding.
Connect QueryWeaver to Claude, Cursor or any other MCP client and it stops being a tab you switch to. An MCP server for Text2SQL: transforms natural language into SQL using graph schema understanding. The queryweaver mcp server is what makes that connection.
QueryWeaver is an open-source Text2SQL tool that converts plain-English questions into SQL using graph-powered schema understanding. It helps you ask databases natural-language questions and returns SQL and results.
QueryWeaver exposes a small REST API for managing graphs (database schemas) and running Text2SQL queries. All endpoints that modify or access user-scoped data require authentication via a bearer token. In the browser the app uses session cookies and OAuth flows; for CLI and scripts you can use an API token (see tokens routes or the web UI to create one).
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Overview — QueryWeaver exposes a small REST API for managing graphs (database schemas) and running Text2SQL queries. All endpoints that modify or accessInstallation — The Installation tool exposed by this serverRequirements — The Requirements tool exposed by this serverPrerequisites — The Prerequisites tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at queryweaver on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: FASTAPI_SECRET_KEY, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET, AZURE_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. QueryWeaver's toolset — Overview, Installation, Requirements and 1 more — is a fair guide to whether it matches your workflow. It is maintained by com.falkordb; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against QueryWeaver's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Overview | QueryWeaver exposes a small REST API for managing graphs (database schemas) and running Text2SQL queries. All endpoints that modify or access user-scoped data require authentication via a bearer token. In the browser the |
| Installation | The Installation tool exposed by this server. |
| Requirements | The Requirements tool exposed by this server. |
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"mcpServers": {
"queryweaver": {
"command": "uvx",
"args": ["queryweaver"],
"env": {
"FASTAPI_SECRET_KEY": "your-value",
"GOOGLE_CLIENT_ID": "your-value",
"GOOGLE_CLIENT_SECRET": "your-value",
"GITHUB_CLIENT_ID": "your-value",
"GITHUB_CLIENT_SECRET": "your-value",
"AZURE_API_KEY": "your-value",
"OPENAI_API_KEY": "your-value",
"GEMINI_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| FASTAPI_SECRET_KEY | Credential the server authenticates with. | Yes |
| GOOGLE_CLIENT_ID | Configuration value read at startup. | Optional |
| GOOGLE_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| GITHUB_CLIENT_ID | Configuration value read at startup. | Optional |
| GITHUB_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| AZURE_API_KEY | Credential the server authenticates with. | Yes |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| GEMINI_API_KEY | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.