[ MCP SERVER SUMMARY ]
Homebrew MCP server summary
Homebrew's official MCP server ships with Homebrew and exposes package search, install, uninstall, upgrade, and contributor commands to AI assistants. Run it through Bifrost to control which package-management tools agents may invoke on shared machines.
| Property | Details |
|---|---|
| Company | Homebrew |
| Connection type | STDIO |
| Authentication | None (local brew mcp-server) |
| Package or endpoint | brew mcp-server |
| Capabilities | brew search / info, Install upgrade uninstall, Contributor commands (style, tests) |
| Official documentation | Homebrew MCP documentation |
Before you start
- Homebrew installed
- macOS or Linux host where Bifrost can spawn brew
What you can do with Homebrew
- Allow agents to search formulae without granting unrestricted brew install
- Centralize Homebrew MCP on a build host instead of every developer Mac
- Audit package installs triggered by coding agents
[ HOW TO CONNECT ]
Connect Homebrew to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Homebrew in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose STDIO. Or register via the API below.
• Official launch command is brew mcp-server (no separate npm package).
• Scope tools carefully — install/uninstall can change the host system.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Homebrew.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Homebrew via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "homebrew",
"connection_type": "stdio",
"stdio_config": {
"command": "brew",
"args": [
"mcp-server"
]
},
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Run Homebrew through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Homebrew MCP server do?
Homebrew exposes brew search / info, install upgrade uninstall, contributor commands (style, tests) to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
How does Homebrew authenticate when used with Bifrost?
Homebrew uses None (local brew mcp-server). Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Can Claude Desktop, Cursor, or Claude Code use Homebrew through Bifrost?
Yes. After registering Homebrew in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
More MCP integrations
GitHub
GitHub's official MCP Server.
JetBrains
Use JetBrains IDE capabilities from MCP-compatible AI assistants, including IntelliJ IDEA and PyCharm workflows.
Playwright
Microsoft’s official browser automation MCP server for navigating pages, interacting with web apps, and running browser-based workflows.