MCP Toolbox for Databases

Content

MCP Toolbox for Databases is an open source MCP server and framework for database-backed tools. It can expose prebuilt database tools for MCP clients or serve custom tools defined in a tools.yaml file. The project documents support for Google Cloud databases and many other systems, including PostgreSQL, MySQL, SQL Server, Oracle, MongoDB, Redis, Elasticsearch, CockroachDB, ClickHouse, Couchbase, Neo4j, Snowflake, and Trino.

Use it when an agent needs database context, schema exploration, or pre-approved database operations without hand-building an MCP server for each database.

Source Review

• https://github.com/googleapis/mcp-toolbox
• https://mcp-toolbox.dev/documentation/introduction/
• https://mcp-toolbox.dev/documentation/configuration/prebuilt-configs/
• https://mcp-toolbox.dev/documentation/configuration/
• https://www.npmjs.com/package/@toolbox-sdk/server

These sources were reviewed on 2026-06-05. Prefer the live documentation for supported database lists, prebuilt tool names, runtime options, authentication support, and configuration schema.

Features

• Prebuilt MCP tools for common database exploration and querying workflows.
• Custom database tools defined through tools.yaml.
• Support for parameterized SQL tools, toolsets, prompts, and source definitions.
• Integrated authentication patterns, connection pooling, and OpenTelemetry observability.
• Compatibility with MCP clients such as Claude Code, Codex, Gemini CLI, Google Antigravity, and other MCP-capable hosts.
• SDKs for application integration in Python, JavaScript/TypeScript, Go, and Java.

Installation

For a basic prebuilt PostgreSQL setup:

claude mcp add toolbox-postgres -- npx -y @toolbox-sdk/server --prebuilt=postgres --stdio

For JSON-based MCP clients:

{
  "mcpServers": {
    "toolbox-postgres": {
      "command": "npx",
      "args": ["-y", "@toolbox-sdk/server", "--prebuilt=postgres", "--stdio"]
    }
  }
}

For custom tools, create a reviewed tools.yaml and run the server with:

npx @toolbox-sdk/server --config tools.yaml

Use Cases

• Let an agent inspect database schemas while generating data-aware application code.
• Expose read-only SQL exploration in a development database.
• Build production-ready, parameterized database tools instead of broad query access.
• Add semantic search or structured data tools to an agent runtime.
• Centralize database access patterns behind a reviewed MCP tool configuration.

Safety and Privacy

Database MCP servers need explicit guardrails. Use least-privilege credentials, prefer read-only accounts for exploration, limit exposed toolsets, and keep production write operations behind reviewed custom tools. Avoid giving an agent unbounded query access to sensitive or expensive databases.

Never commit database credentials, IAM secrets, service account keys, or connection strings. Treat schemas, row samples, query errors, and trace metadata as potentially sensitive.

Duplicate Check

Existing entries cover specific database MCP servers such as BigQuery, PostgreSQL, MongoDB, Snowflake, ClickHouse, Redis, and Qdrant. This entry covers Google's broader MCP Toolbox for Databases project and its reusable server/tool framework.

• Source repositorygithub.com 2026-07-21T01:31:08+00:00
• Documentationmcp-toolbox.dev
• Submitted by oktofeesh12026-06-05