Homebrew MCP Python Server

What is Homebrew MCP Python Server?

A Model Context Protocol (MCP) server for Homebrew package management on macOS, designed for integration with Claude Desktop and other MCP-compatible clients. It exposes Homebrew commands as MCP tools for use by LLM clients.

How to use Homebrew MCP Python Server?

Install via cloning the repo, setting up a uv-managed Python virtual environment, and installing dependencies. For Claude Desktop, configure ~/Library/Application Support/Claude/claude_desktop.json with a uv run command pointing to the project. For Cursor, use the provided "Add to Cursor" button or manually edit ~/.cursor/mcp.json. The server runs via stdio and logs to homebrew_mcp.log.

Key features of Homebrew MCP Python Server

• Exposes Homebrew commands as MCP tools (install, search, doctor, etc.)
• Runs real brew commands via subprocess on macOS
• Fully MCP spec-compliant (stdio, JSON-RPC 2.0)
• Designed for Claude Desktop and other LLM clients
• Functional, declarative Python (no classes)
• Logs all requests/results to homebrew_mcp.log

Use cases of Homebrew MCP Python Server

• Let Claude Desktop install, uninstall, or upgrade Homebrew packages
• Ask an LLM to check Homebrew system health with brew doctor
• Get a summary of installed packages or search for new ones
• Automate package management tasks via chat interface
• Test MCP tool interactions with the included test script

FAQ from Homebrew MCP Python Server

What is Homebrew MCP Python Server and what does it do?

It is an MCP server that turns Homebrew commands (install, search, doctor, etc.) into tools that MCP client applications like Claude Desktop can call directly.

What are the dependencies/runtime requirements?

Requires macOS, Homebrew installed, Python 3.13, and the uv dependency manager. The MCP Python SDK and Anthropic SDK (for the test script) are installed via requirements.txt.

Where do logs and data live?

Logs are written to homebrew_mcp.log in the project directory. The server runs real brew commands, so package data resides in the normal Homebrew locations. The virtual environment is in .venv.

What transports and authentication does it use?

It uses stdio transport (MCP spec 2025-06-18) with JSON-RPC 2.0 messaging. No authentication is built-in; it relies on local machine access.

Can it be used with clients other than Claude Desktop?

Yes, it is designed for any MCP-compatible client. The README includes specific integration instructions for Cursor and demonstrates interaction with Claude via the Anthropic API test script.