MCP Toolbox for Databases
Google CloudMCP server from Google that connects agents, IDEs and applications to databases. Started with a prebuilt configuration, it gives an MCP client ready-made tools for exploring schemas and running SQL against Google Cloud databases such as BigQuery, AlloyDB, Spanner and Cloud SQL, and against PostgreSQL, MySQL, MongoDB, Snowflake and others. Defined in a tools.yaml file, it serves custom tools built on fixed queries, with connection pooling, IAM authentication and OpenTelemetry tracing. It was first released as Gen AI Toolbox for Databases.
Openness
5 high confidence- license
- Apache-2.0 (OSI)
- source
- public
- core features withheld
- no — the server, its prebuilt configurations and the custom-tools framework are all in the Apache-2.0 repository; Google's managed MCP servers for its databases are a separate product, which the README points to as the managed alternative
MCP Toolbox is released under Apache-2.0, and the whole server, prebuilt database tools and custom-tools framework included, builds and runs from the public repository. Google sells managed MCP servers for its own databases, but as a separate product, not as a paid edition of this one.
- https://raw.githubusercontent.com/googleapis/mcp-toolbox/main/LICENSE recorded 2026-11-12
The LICENSE is the full "Apache License, Version 2.0, January 2004" text.
- https://raw.githubusercontent.com/googleapis/mcp-toolbox/main/README.md recorded 2026-11-12
The README calls it "an open source Model Context Protocol (MCP) server" with a "Ready-to-use MCP Server" and a "Custom Tools Framework", installs it as a release binary, container image or "npx @toolbox-sdk/server", and says "For users looking for a managed solution, Google Cloud MCP Servers provide a managed MCP experience with prebuilt tools".
- https://registry.npmjs.org/@toolbox-sdk/server/latest recorded 2026-11-12
The npm record for @toolbox-sdk/server 1.16.0 declares "license":"Apache-2.0", author "Google LLC", description "A CLI tool for running a toolbox server." and repository git+https://github.com/googleapis/mcp-toolbox.git.
Adoption
3 medium confidenceAdoption is the trailing month of npm downloads of @toolbox-sdk/server, the launcher the README's MCP configuration runs through npx. The release binary and container image, which the README recommends for production, are not counted, and the client SDKs are left out because they only call a running server.
- https://api.npmjs.org/downloads/point/last-month/@toolbox-sdk/server recorded 2026-11-12
194,294 downloads of @toolbox-sdk/server between 2026-10-12 and 2026-11-10
- https://raw.githubusercontent.com/googleapis/mcp-toolbox/main/README.md recorded 2026-11-12
The README notes the npx route "is optimized for convenience rather than performance" and points "For a more standard and reliable installation" to "the binary or container image".
Capability
3 medium confidenceMCP Toolbox exposes one kind of system, a database, through prebuilt or custom tools, and the connection details and credentials are the caller's to set in environment variables or tools.yaml. It hosts nothing and holds no logins on anyone's behalf, which keeps it level with Postgres MCP Pro however many engines it can reach.
- https://raw.githubusercontent.com/googleapis/mcp-toolbox/main/README.md recorded 2026-11-12
The README's prebuilt tools give "list_tables" and "execute_sql" against AlloyDB, BigQuery, Cloud SQL, Spanner, PostgreSQL, MySQL, MongoDB, Snowflake and others, after the user sets "the appropriate environment variables to connect"; a custom source in tools.yaml carries host, database, user and password.
Verified 2026-11-12, except some scores, still awaiting re-confirmation