Ha MCP vs Git

A side-by-side look at the Ha MCP and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Ha MCP logoHa MCPHome AutomationComprehensive Model Context Protocol server for managing Home Assistant through AI assistants.44FairAuth: api key requiredGit logoGitVersion Control · Local subprocess (stdio)Tools to read, search, and manipulate Git repositories.81ExcellentAuth: no auth required

Verdict: choose Ha MCP for home automation work; choose Git for version control as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Ha MCP logoChoose Ha MCP when

  • You need dedicated capabilities in the Home Automation domain.
  • Its auth model fits you: API key required.
  • You have the keys it needs: HOMEASSISTANT_URL, HOMEASSISTANT_TOKEN.
Explore Ha MCP

Git logoChoose Git when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like repo_path, context_lines, target.
Explore Git

Feature & specification comparison

Rows where the two servers differ are marked.

SpecHa MCP logoHa MCPGit logoGit
CategoryHome AutomationVersion Control
Quality signal44/100 · Fair81/100 · Excellent
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthAPI key requiredNo auth required
PricingFreeFree
Required env varsHOMEASSISTANT_URLHOMEASSISTANT_TOKENNone listed
Verified ownerCommunity listing Verified
GitHub stars5,18691,526
Directory activity 0 views 0 installs 0 upvotes 51 views 0 installs 0 upvotes
ToolsNot listed16

Tools & capabilities

Ha MCP tools

No tool names declared yet. Check the project README from the listing page.

Git tools 16

  • repo_path
  • context_lines
  • target
  • message
  • MERGE_HEAD
  • HEAD
  • files
  • max_count
  • start_timestamp
  • end_timestamp
  • branch_name
  • base_branch
  • +4 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Ha MCP

No confirmed install command for Ha MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

Git

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "installations"
      ]
    }
  }
}

Frequently asked questions

Ha MCP is categorized under Home Automation and uses an install path we have not confirmed yet. Git belongs to Version Control and uses a local stdio subprocess. Pick Ha MCP for home automation work and Git for version control.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Ha MCP has no confirmed install command yet — follow its own setup instructions.

Ha MCP is listed as free. Auth: api key required. Git is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add ha-mcp and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Ha MCP has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 5,186 GitHub stars. Git has 81/100 (Excellent) with 51 views, 0 installs and 91,526 GitHub stars.