MCP Toolbox for Databases
@googleapis
About MCP Toolbox for Databases
MCP Toolbox for Databases is an open source MCP server for databases.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"toolbox": {
"command": "./toolbox",
"args": [
"--stdio"
]
}
}
}Tools
1name
Overview
What is MCP Toolbox for Databases?
MCP Toolbox for Databases is an open source Model Context Protocol (MCP) server that connects AI agents, IDEs, and applications directly to enterprise databases. It serves a dual purpose: a ready‑to‑use prebuilt server with generic tools for instant data exploration, and a custom tools framework for building secure, production‑grade AI tools.
How to use MCP Toolbox for Databases?
For prebuilt tools, configure an MCP client (e.g., Gemini CLI, Claude Code) to run npx @toolbox-sdk/server --prebuilt=<database> and set the required environment variables. For custom tools, define a tools.yaml file with sources, tools, toolsets, and prompts, then run npx @toolbox-sdk/server --config tools.yaml. The server can also be installed as a binary or run via Docker.
Key features of MCP Toolbox for Databases
- Out‑of‑the‑box database access with prebuilt generic tools
- Custom tools framework for building safe, production‑ready tools
- Handles connection pooling, integrated auth (IAM), and OpenTelemetry
- Enhanced security with integrated authentication
- Simplified development (integrate in less than 10 lines of code)
- End‑to‑end observability with built‑in metrics and tracing
Use cases of MCP Toolbox for Databases
- Query databases in plain English from your IDE or CLI
- Automate schema discovery and management
- Generate database‑aware code without context switching
- Build specialized AI tools with restricted access and semantic search
- Integrate database tools into LangChain, LlamaIndex, or custom agents
FAQ from MCP Toolbox for Databases
What databases does MCP Toolbox for Databases support?
Supported databases include Google Cloud databases (AlloyDB, BigQuery, Cloud SQL, Spanner, Firestore, Knowledge Catalog) and third‑party databases (PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, MongoDB, Redis, Elasticsearch, CockroachDB, ClickHouse, Couchbase, Neo4j, Snowflake, Trino, and more).
How do I install and run MCP Toolbox for Databases?
You can run it directly with npx @toolbox-sdk/server --config tools.yaml, or download a prebuilt binary from the releases page for Linux, macOS, or Windows. Container images are also available.
How do I configure custom tools?
Create a tools.yaml file with kind: source, kind: tool, kind: toolset, and kind: prompt sections. Then start the server with the --config tools.yaml flag. Detailed reference is available in the full documentation.
What is the difference between the self‑hosted Toolbox and Google Cloud MCP Servers?
Google Cloud MCP Servers provide a managed MCP experience with prebuilt tools. The open‑source Toolbox is self‑hosted and also offers a custom tools framework. More details can be found in the FAQ.
How does MCP Toolbox for Databases handle authentication and observability?
It supports integrated authentication (IAM) for secure access and provides end‑to‑end observability with built‑in support for OpenTelemetry metrics and tracing, all out of the box.
Frequently asked questions
What databases does MCP Toolbox for Databases support?
Supported databases include Google Cloud databases (AlloyDB, BigQuery, Cloud SQL, Spanner, Firestore, Knowledge Catalog) and third‑party databases (PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, MongoDB, Redis, Elasticsearch, CockroachDB, ClickHouse, Couchbase, Neo4j, Snowflake, Trino, and more).
How do I install and run MCP Toolbox for Databases?
You can run it directly with `npx @toolbox-sdk/server --config tools.yaml`, or download a prebuilt binary from the releases page for Linux, macOS, or Windows. Container images are also available.
How do I configure custom tools?
Create a `tools.yaml` file with `kind: source`, `kind: tool`, `kind: toolset`, and `kind: prompt` sections. Then start the server with the `--config tools.yaml` flag. Detailed reference is available in the full documentation.
What is the difference between the self‑hosted Toolbox and Google Cloud MCP Servers?
Google Cloud MCP Servers provide a managed MCP experience with prebuilt tools. The open‑source Toolbox is self‑hosted and also offers a custom tools framework. More details can be found in the [FAQ](https://mcp-toolbox.dev/dev/reference/faq/).
How does MCP Toolbox for Databases handle authentication and observability?
It supports integrated authentication (IAM) for secure access and provides end‑to‑end observability with built‑in support for OpenTelemetry metrics and tracing, all out of the box.
Basic information
More Other MCP servers
MCP Registry
modelcontextprotocolA community driven registry service for Model Context Protocol (MCP) servers.
MCP Go 🚀
mark3labsA Go implementation of the Model Context Protocol (MCP), enabling seamless integration between LLM applications and external data sources and tools.
Activepieces
activepiecesAI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
ICSS
chokcoco不止于 CSS
Production-ready MCP integrations for AI applications
Klavis-AIKlavis AI: MCP integration platforms that let AI agents use tools reliably at any scale
Comments