MCP Toolbox for Databases
io.github.googleapisPublished by GitHub account googleapisv1.16.0Updated Nov 6, 2026
MCP Toolbox for Databases enables your agent to connect to your database.
Overview
Open-source MCP server that connects an AI assistant to enterprise and open-source databases for schema exploration, SQL queries and custom tools.
- What you can do
- List tables and run SQL against a connected database using prebuilt generic tools
- Explore schemas and generate database-aware code from an IDE or CLI
- Load only a chosen toolset, such as SQL-only tools for a given database
- Define custom tools, sources, toolsets, prompts and read-only resources in a YAML config
- Serve tools to agents through client SDKs for Python, JavaScript, Go and agent frameworks
- Generate portable Agent Skills from a toolset and export traces and metrics via OpenTelemetry
- When to use it
- Useful when an assistant should query or explore a database in plain language, or when a team wants to expose curated, restricted SQL tools to production agents instead of raw database access.
- Requirements
- Runs locally as a binary, container image, Homebrew package, Go source build, or via npx with Node.js. Needs a tools.yaml config or a prebuilt database flag, plus connection details and credentials for each database source. Google Cloud sources may use IAM authentication.
Installation
In SourceWeft
- Open MCP Toolbox for Databases in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
MCP Toolbox for Databases
[googleapis%2Fmcp-toolbox | Trendshift]
MCP Toolbox for Databases is an open source Model Context Protocol (MCP) server that connects your AI agents, IDEs, and applications directly to your enterprise databases.
It serves a dual purpose:
- Ready-to-use MCP Server (Build-Time): Instantly connect Gemini CLI, Google Antigravity, Claude Code, Codex, or other MCP clients to your databases using our prebuilt generic tools. Talk to your data, explore schemas, and generate code without writing boilerplate.
- Custom Tools Framework (Run-Time): A robust framework to build specialized, highly secure AI tools for your production agents. Define structured queries, semantic search, and NL2SQL capabilities safely and easily.
This README provides a brief overview. For comprehensive details, see the full documentation.
[!IMPORTANT]
Repository Name Update: Thegenai-toolboxrepository has been officially renamed tomcp-toolbox. To ensure your local environment reflects the new name, you may update your remote:git remote set-url origin https://github.com/googleapis/mcp-toolbox.git
[!NOTE] This solution was originally named “Gen AI Toolbox for Databases” (github.com/googleapis/genai-toolbox) as its initial development predated MCP, but was renamed to align with the MCP compatibility.
Table of Contents
- Why MCP Toolbox?
- Quick Start: Prebuilt Tools
- Quick Start: Custom Tools
- Install & Run the Toolbox server
- Connect to Toolbox
- Additional Features
- Versioning
- Contributing
- Community
Why MCP Toolbox?
- Out-of-the-Box Database Access: Prebuilt generic tools for instant data exploration (e.g.,
list_tables,execute_sql) directly from your IDE or CLI. - Custom Tools Framework: Build production-ready tools with your own predefined logic, ensuring safety through Restricted Access, Structured Queries, and Semantic Search.
- Simplified Development: Integrate tools into your Agent Development Kit (ADK), LangChain, LlamaIndex, or custom agents in less than 10 lines of code.
- Better Performance: Handles connection pooling, integrated auth (IAM), and end-to-end observability (OpenTelemetry) out of the box.
- Enhanced Security: Integrated authentication for more secure access to your data.
- End-to-end Observability: Out of the box metrics and tracing with built-in support for OpenTelemetry.
Quick Start: Prebuilt Tools
Stop context-switching and let your AI assistant become a true co-developer. By connecting your IDE to your databases with MCP Toolbox, you can query your data in plain English, automate schema discovery and management, and generate database-aware code.
You can use the Toolbox in any MCP-compatible IDE or client (e.g., Gemini CLI, Google Antigravity, Claude Code, Codex, etc.) by configuring the MCP server.
Prebuilt tools are also conveniently available via the Google Antigravity MCP Store with a simple click-to-install experience.
-
Add the following to your client's MCP configuration file (usually
mcp.jsonorclaude_desktop_config.json): -
Set the appropriate environment variables to connect, see the Prebuilt Tools Reference.
When you run Toolbox with a --prebuilt=<database> flag, you instantly get access to standard tools to interact with that database. You can also specify a specific toolset using the --prebuilt=<database>/<toolset> syntax (e.g., --prebuilt=postgres/data to only load SQL tools).
Supported databases currently include:
- Google Cloud: AlloyDB, BigQuery, Cloud SQL (PostgreSQL, MySQL, SQL Server), Spanner, Firestore, Knowledge Catalog (formerly known as Dataplex).
- Other Databases: PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, MongoDB, Redis, Elasticsearch, CockroachDB, ClickHouse, Couchbase, Neo4j, Snowflake, Trino, and more.
For a full list of available tools and their capabilities across all supported databases, see the Prebuilt Tools Reference.
See the Install & Run the Toolbox server section for different execution methods like Docker or binaries.
[!TIP] For users looking for a managed solution, Google Cloud MCP Servers provide a managed MCP experience with prebuilt tools; you can learn more about the differences here.
Quick Start: Custom Tools
Toolbox can also be used as a framework for customized tools.
The primary way to configure Toolbox is through the tools.yaml file. If you
have multiple files, you can tell Toolbox which to load with the --config tools.yaml flag.
You can find more detailed reference documentation to all resource types in the Resources.
Sources
The sources section of your tools.yaml defines what data sources your
Toolbox should have access to. Most tools will have at least one source to
execute against.
For more details on configuring different types of sources, see the Sources.
Tools
The tools section of a tools.yaml define the actions an agent can take: what
type of tool it is, which source(s) it affects, what parameters it uses, etc.
For more details on configuring different types of tools, see the Tools.
Toolsets
The toolsets section of your tools.yaml allows you to define groups of tools
that you want to be able to load together. This can be useful for defining
different groups based on agent or application.
Prompts
The prompts section of a tools.yaml defines prompts that can be used for
interactions with LLMs.
For more details on configuring prompts, see the Prompts.
Resources
The resources and resourceTemplates sections of your tools.yaml define read-only
content, files, or parameterized directory trees that can be discovered and retrieved
by MCP clients:
For more details on configuring resources and resource templates, see Resources.
Install & Run the Toolbox server
You can run Toolbox directly with a configuration file:
This runs the latest version of the Toolbox server with your configuration file.
[!NOTE] This method is optimized for convenience rather than performance. For a more standard and reliable installation, please use the binary or container image as described in Install & Run the Toolbox server.
Install Toolbox
For the latest version, check the releases page and use the following instructions for your OS and CPU architecture.
Binary
To install Toolbox as a binary:
Linux (AMD64)
To install Toolbox as a binary on Linux (AMD64):
macOS (Apple Silicon)
To install Toolbox as a binary on macOS (Apple Silicon):
macOS (Intel)
To install Toolbox as a binary on macOS (Intel):
Windows (Command Prompt)
To install Toolbox as a binary on Windows (Command Prompt):
Windows (PowerShell)
To install Toolbox as a binary on Windows (PowerShell):
Windows ARM64 (Command Prompt)
To install Toolbox as a binary on Windows ARM64 (Command Prompt):
Windows ARM64 (PowerShell)
To install Toolbox as a binary on Windows ARM64 (PowerShell):
Container image
You can also install Toolbox as a container:Homebrew
To install Toolbox using Homebrew on macOS or Linux:
Compile from source
To install from source, ensure you have the latest version of Go installed, and then run the following command:
Gemini CLI
Check out the [Gemini CLI extensions](https://geminicli.com/extensions/) to install prebuilt tools for specific databases like AlloyDB, BigQuery, and Cloud SQL directly into Gemini CLI.Interact with your custom tools using natural language through the Gemini CLI.
Run Toolbox
Configure a tools.yaml to define your tools, and then
execute toolbox to start the server:
Binary
To run Toolbox from binary:
ⓘ Note
Toolbox enables dynamic reloading by default. To disable, use the--disable-reloadflag.
Container image
To run the server after pulling the container image:
ⓘ Note
The-vflag mounts your localtools.yamlinto the container, and-pmaps the container's port5000to your host's port5000.
Source
To run the server directly from source, navigate to the project root directory and run:
ⓘ Note
This command runs the project from source, and is more suitable for development and testing. It does not compile a binary into your$GOPATH. If you want to compile a binary instead, refer the Developer Documentation.
Homebrew
If you installed Toolbox using Homebrew, the toolbox
binary is available in your system path. You can start the server with the same
command:
NPM
To run Toolbox directly without manually downloading the binary (requires Node.js):
Gemini CLI
After installing a [Gemini CLI extensions](https://geminicli.com/extensions/), the prebuilt tools will be available during use.You can use toolbox help for a full list of flags! To stop the server, send a
terminate signal (ctrl+c on most platforms).
For more detailed documentation on deploying to different environments, check out the resources in the Deploy Toolbox section
Connect to Toolbox
Once your Toolbox server is up and running, you can load tools into your MCP-compatible client or application.
MCP Client
Add the following configuration to your MCP client configuration:
If you would like to connect to a specific toolset, replace url with "http://127.0.0.1:5000/mcp/{toolset_name}".
Toolbox SDKs: Integrate with your Application
Toolbox Client SDKs provide the easy-to-use building blocks and advanced features for connecting your custom applications to the MCP Toolbox server. See below the list of Client SDKs for using various frameworks:
Python (Github)
Core
Install Toolbox Core SDK:
Load tools:
For more detailed instructions on using the Toolbox Core SDK, see the project's README.
LangChain / LangGraph
Install Toolbox LangChain SDK:
Load tools:
For more detailed instructions on using the Toolbox LangChain SDK, see the project's README.
LlamaIndex
Install Toolbox Llamaindex SDK:
Load tools:
For more detailed instructions on using the Toolbox Llamaindex SDK, see the project's README.
Javascript/Typescript (Github)
Core
Install Toolbox Core SDK:
Load tools:
For more detailed instructions on using the Toolbox Core SDK, see the project's README.
LangChain / LangGraph
Install Toolbox Core SDK:
Load tools:
Genkit
Install Toolbox Core SDK:
Load tools:
ADK
Install Toolbox ADK SDK:
Load tools:
For more detailed instructions on using the Toolbox ADK SDK, see the project's README.
Go (Github)
Core
Install Toolbox Go SDK:
Load tools:
For more detailed instructions on using the Toolbox Go SDK, see the project's README.
LangChain Go
Install Toolbox Go SDK:
Load tools:
Genkit
Install Toolbox Go SDK:
Load tools:
Go GenAI
Install Toolbox Go SDK:
Load tools:
OpenAI Go
Install Toolbox Go SDK:
Load tools:
ADK Go
Install Toolbox Go SDK:
Load tools:
For more detailed instructions on using the Toolbox Go SDK, see the project's README.
Additional Features
Test tools with the Toolbox UI
To launch Toolbox's interactive UI, use the --ui flag. This allows you to test
tools and toolsets with features such as authorized parameters. To learn more,
visit Toolbox UI.
Telemetry
Toolbox emits traces and metrics via OpenTelemetry. Use --telemetry-otlp=<endpoint>
to export to any OTLP-compatible backend like Google Cloud Monitoring, Agnost AI, or
others. See the telemetry docs for details.
Generate Agent Skills
The skills-generate command allows you to convert a toolset into an Agent Skill compatible with the Agent Skill specification. This is useful for distributing tools as portable skill packages.
Once generated, you can install the skill into the Gemini CLI:
For more details, see the Generating Skills guide. To serve a skill you already have over MCP, see Serving Skills over MCP.
The repository also ships ready-to-use Agent Skills (e.g. maintainer workflows). See skills/ for the catalog and install instructions.
Versioning
MCP Toolbox for Databases follows Semantic Versioning.
The Public API includes the Toolbox Server (CLI, configuration manifests, and pre-built toolsets) and the Client SDKs.
- Major versions are incremented for breaking changes, such as incompatible CLI or manifest changes.
- Minor versions are incremented for new features, including modifications to pre-built toolsets or beta features.
- Patch versions are incremented for backward-compatible bug fixes.
For more details, including our Container Tagging Policy, see our Full Versioning Policy.
Contributing
Contributions are welcome. Please, see the CONTRIBUTING guide to get started.
For technical details on setting up a environment for developing on Toolbox itself, see the DEVELOPER guide.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. See Contributor Code of Conduct for more information.
Community
Join our Discord community to connect with our developers!
Source: README.md at commit 06ea49d
Tools
0Version history
7- v1.16.0LatestNov 6, 2026
- v1.15.0Oct 23, 2026
- v1.14.0Oct 9, 2026
- v1.13.1Sep 26, 2026
- v1.13.0Sep 25, 2026
- v1.12.0Sep 18, 2026
- v1.11.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts