Homebrew MCP Server

Homebrew mcp mcp server lets Claude, Cursor and other MCP clients work with Homebrew MCP directly. Interact with Homebrew (the package manager for macOS and Linux) using natural language commands.

What Homebrew MCP does

A Model Context Protocol (MCP) server for Homebrew package management on macOS, designed for seamless integration with Claude Desktop and other MCP-compatible clients.

Key capabilities

• Exposes Homebrew commands as MCP tools. The supported commands are grouped by function:
• Package Management: — install, uninstall, upgrade, cleanup
• Information & Discovery: — list, search, info, outdated, deps
• System Health & Updates: — doctor, update
• Tap & Source Management: — tap, untap
• Version Management: — pin, unpin
• Service Management: — services
• Runs real brew commands via subprocess (requires Homebrew on macOS)

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• Language — ** Python 3.13
• MCP — ** Model Context Protocol
• homebrew_mcp.py — Main MCP server script
• test_claude_homebrew_mcp.py — Interactive Claude integration test script
• Configuration — claude_desktop_config.json — Example configuration for Claude Desktop
• mcp.json — Example configuration for Cursor
• requirements.txt — Python project dependencies
• README.md — This file
• homebrew_mcp.log — Log file for the MCP server
• macOS — ** Sonoma 14.7.5
• Homebrew — ** 4.5.8
• Cursor — ** 1.1.4
• Browsers — google-chrome, firefox
• Development — visual-studio-code, iterm2, cursor, github

Installing the homebrew mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply one environment variable: ANTHROPIC_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Homebrew MCP sits in that group, and the shape of its toolset — Language, MCP, homebrew_mcp.py among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Homebrew MCP.
• Written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the homebrew mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.