MCP Toolbox for Databases in Cline schema-aware coding, query-checked answers.
Hook Google's MCP Toolbox for Databases into Cline so the VS Code agent can run your sanctioned queries while it codes. The config lives in cline_mcp_settings.json, reached through Cline's own MCP panel.
When Cline writes code against your database, it's guessing at the schema unless something lets it look. MCP Toolbox for Databases (github.com/googleapis/genai-toolbox, 15.5k stars) is Google's answer: an MCP server where you declare database sources and named query tools in a tools.yaml, and the agent gets those tools — no open-ended SQL channel.
Cline stores MCP servers in cline_mcp_settings.json, buried in VS Code's globalStorage under saoudrizwan.claude-dev/settings/. You never need to hunt for that path: the Cline panel's MCP Servers view has a Configure action that opens the file directly.
Get the prerequisites in place
The Toolbox ships as an OCI container image, so Docker must be installed and running. Write a tools.yaml with one source — supported engines include PostgreSQL, MySQL, SQL Server, BigQuery, and Spanner; check the repo for the full list — and a handful of read-only tools. Cline will happily iterate against whatever you expose, so expose deliberately.
Configure through the Cline panel
Open the Cline sidebar, click the MCP Servers icon, then Configure MCP Servers — VS Code opens cline_mcp_settings.json. Add the Toolbox under mcpServers. The disabled and autoApprove fields are Cline-specific: leave autoApprove empty until you trust the tool set.
{
"mcpServers": {
"toolbox": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-v", "/Users/you/db/tools.yaml:/config/tools.yaml",
"us-central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:latest",
"--tools-file", "/config/tools.yaml",
"--stdio"
],
"disabled": false,
"autoApprove": []
}
}
}Watch it go green
Cline picks up the file on save — no full VS Code restart needed in the normal case. The MCP Servers panel shows each server with a status indicator and its tool list expanded beneath it. When the Toolbox connects, your tools.yaml tool names appear there. In a task, Cline will propose Toolbox calls inline and wait for your approval unless you've added the tool to autoApprove.
Troubleshooting in Cline
A red status in the MCP panel means the launch command failed. Click into the server's row — Cline surfaces the process error there — or run the docker command yourself in a terminal, where the Toolbox's startup errors (invalid tools.yaml, unreachable source) print plainly to stderr.
Specific traps for this stack: docker run must include -i or the stdio session closes before the handshake; the host side of the -v mount must be an absolute path; and a database listening on your machine is host.docker.internal from the container's perspective, not localhost. If the panel seems stuck on an old config, use the restart action next to the server or reload the VS Code window — and remember the file is per-machine globalStorage, so a teammate cloning your repo doesn't inherit it.
The live listing
The Toolbox's live listing on the Loomal marketplace — https://loomal.ai/marketplace/mcp-toolbox-for-databases — shows its probed tools so you can scope your tools.yaml against what agents actually see. If you ship your own MCP server, claiming its Loomal listing verifies ownership and enables per-call pricing.
FAQ
How do I install the Toolbox for Databases in Cline?
Open the Cline panel > MCP Servers > Configure, which opens cline_mcp_settings.json, and add a docker run entry under mcpServers that mounts your tools.yaml with --tools-file and --stdio flags. Cline reconnects on save and lists the tools in the panel.
Where is Cline's MCP settings file?
Inside VS Code's globalStorage at saoudrizwan.claude-dev/settings/cline_mcp_settings.json. Don't navigate there manually — the Configure button in Cline's MCP Servers panel opens the exact file, which avoids editing the wrong profile's storage.
Why is the server red in the MCP panel?
The docker command exited at startup. Run it by hand in a terminal: you'll see whether it's a missing -i flag, a relative mount path, a tools.yaml validation error, or the database being unreachable from inside the container (use host.docker.internal for host databases).
Should I use autoApprove for database tools?
Only for tools you've watched behave — and ideally only read-only ones. Anything that writes to the database deserves the per-call approval prompt; the whole point of the Toolbox's named-tool design is that you stay in control of what executes.
Browse more MCP servers for Cline.
Every Loomal listing carries a live-probed tool list.