Install mcp-toolbox with Homebrew

Project links

• Homepage

Commands and aliases

• toolbox

Project history

The project began publicly on GitHub in June 2024 under the Google APIs organization as Gen AI Toolbox for Databases. Its own README notes that the initial development predated MCP and that the repository was later renamed from `genai-toolbox` to `mcp-toolbox` to align with MCP compatibility.

By 2026 the project documentation had moved to the `mcp-toolbox.dev` documentation site, with dedicated sections for configuration, sources, tools, toolsets, prompts, SDKs, deployment, and database-specific integrations. The package is distributed as a command-line server binary, Docker/container artifact, and SDK-adjacent tooling, with the Homebrew formula exposing the `toolbox` executable.

Adoption history

The official README positions Toolbox for use with MCP-compatible IDEs and clients including Gemini CLI, Google Antigravity, Claude Code, Codex, and other MCP clients. It also documents integration paths for ADK, LangChain, LlamaIndex, and custom agents, which made it relevant beyond a single chat client.

GitHub repository metadata showed substantial public adoption by July 2026, with roughly 15.8k stars and 1.6k forks. The project's releases began with v0.0.1 in October 2024 and reached v1.6.0 on July 1, 2026, signaling rapid development across the first two years of the MCP wave.

How it is used

Typical package-manager usage is to install the `toolbox` binary and either run prebuilt database tools with flags such as `--prebuilt=postgres` or run a custom configuration with `--config tools.yaml`. The README documents a `tools.yaml` model containing sources, tools, toolsets, and prompts, while the docs expand that into database-specific source and tool reference pages.

The package is especially aimed at database-aware assistant workflows: listing schemas, executing SQL, wrapping predefined production queries, adding semantic search or NL2SQL features, and using authentication, connection pooling, and observability rather than handing every MCP client a raw database script.

Why package nerds care

For package-history purposes, MCP Toolbox is a representative example of a large vendor-backed MCP server becoming a packaged CLI. It matters because it turns database access for agent tools into something installable, versioned, and documented across clients, rather than a pile of per-client JSON snippets and local scripts.

It is also notable for its rename: package records may still carry `genai-toolbox` URLs, while the official repository and documentation now use `mcp-toolbox`. That makes it a useful case where package metadata, repository redirects, and documentation URLs can diverge during a young ecosystem's naming cleanup.

Timeline

• 2024-06: Public GitHub repository created as the project that became MCP Toolbox for Databases.
• 2024-10: v0.0.1 release published.
• 2025: Project renamed from Gen AI Toolbox for Databases / genai-toolbox to MCP Toolbox / mcp-toolbox to match MCP compatibility.
• 2026-07: v1.6.0 release published; official docs list broad database integrations and MCP client connection guides.

Related projects

• Related projects include MCP clients such as Claude Code, Codex, Gemini CLI, and IDE integrations, plus agent frameworks such as ADK, LangChain, and LlamaIndex. Within the same package set it is adjacent to MCPHost, MCPM, and mcptools, but focused specifically on database-backed tools rather than client hosting or registry management.

Sources

• https://api.github.com/repos/googleapis/mcp-toolbox
• https://api.github.com/repos/googleapis/mcp-toolbox/releases
• https://github.com/googleapis/mcp-toolbox
• https://mcp-toolbox.dev/