MDBP enables secure database access for LLMs. Instead of generating raw SQL, LLMs produce structured **intent** objects. MDBP validates these intents
If you already use Model Database Protocol, the model database protocol mcp server is the piece that lets your assistant work with it directly. MDBP enables secure database access for LLMs. Instead of generating raw SQL, LLMs produce structured intent objects. MDBP validates these intents against a schema registry, enforces access policies, builds parameterized queries via.
An intent is a structured JSON object that describes a database operation. Every intent contains these core fields:
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Pipeline — The Pipeline tool exposed by this serverHAVING — The HAVING tool exposed by this serverRETURNING — The RETURNING tool exposed by this serverUNION — intersect and except intents are also supported in the same waymdbp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: DATABASE_URL. 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.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Model Database Protocol's toolset — Pipeline, HAVING, RETURNING and 1 more — is a fair guide to whether it matches your workflow. It is maintained by dorukyelken; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Pipeline | The Pipeline tool exposed by this server. |
| HAVING | The HAVING tool exposed by this server. |
| RETURNING | The RETURNING tool exposed by this server. |
| UNION | intersect and except intents are also supported in the same way. |
{
"mcpServers": {
"model-database-protocol": {
"command": "uvx",
"args": ["mdbp"],
"env": {
"DATABASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DATABASE_URL | Endpoint or connection string the server talks to. | 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.