MCP Toolbox For Databases
Give Claude Code or Cursor governed, config-driven SQL and database tools without hand-wiring every query in your agent project.
Overview
MCP Toolbox for Databases is an MCP server for the Build phase that exposes YAML-configured database tools so agents can query your data safely over streamable HTTP.
What is this MCP server?
- Streamable HTTP MCP endpoint with OCI image googleapis/mcp-toolbox v1.4.0
- Declarative tools.yaml (or merged --configs / --config-folder) to expose only approved queries
- Runtime flags for --config, --address, and host/port URL templating
- Designed for agents to run parameterized database operations instead of raw connection strings in prompts
- Google-maintained MCP Toolbox for Databases lineage on GitHub
- Server schema version 1.4.0 in registry metadata
- Default tool config file name tools.yaml via --config
- Transport type streamable-http at http://{host}:{port}/mcp
Community signal: 15.5k GitHub stars.
What problem does it solve?
Agents need live database answers during development, but handing them open SQL and connection strings is risky and tedious to maintain per client.
Who is it for?
Solo builders with an existing cloud or local database who want MCP-gated tools for support queries, admin tasks, and feature debugging.
Skip if: Teams with no database yet, or anyone who needs a full ORM/codegen layer instead of an MCP tool gateway.
What do I get? / Deliverables
After you register the toolbox URL and tools.yaml, your agent invokes named, parameterized database tools instead of improvising connections in every session.
- HTTP MCP endpoint serving merged YAML-defined database tools
- Agent-callable named queries aligned with your schema policies
- Repeatable local or cloud deployment via OCI image 1.4.0
Recommended MCP Servers
Journey fit
Database access is wired while you are building product features and agent backends, not during initial market research. Toolbox sits between your app or agent and managed databases via MCP—classic build-phase integration work.
How it compares
YAML-governed database MCP gateway, not a hosted analytics dashboard or a single-purpose ORM skill.
Common Questions / FAQ
Who is MCP Toolbox For Databases for?
Indie developers and small teams using Claude Code, Cursor, or similar MCP clients who already run a database and want the agent to call pre-approved queries.
When should I use MCP Toolbox For Databases?
Use it during Build when you are integrating your agent or app with Postgres, Spanner, or other supported stores and need repeatable, config-driven tools.
How do I add MCP Toolbox For Databases to my agent?
Run the v1.4.0 OCI image with a tools.yaml (--config), set --address/host/port, then add the http://{host}:{port}/mcp streamable-http remote in your MCP client settings.