MCP Homeassistant vs Git
A side-by-side look at the MCP Homeassistant and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Homeassistant for home automation work as a local process; 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?
Choose MCP Homeassistant when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HA_URL, HA_TOKEN. - You want tools like
get_api_status, get_config, get_components.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Home Automation | Version Control |
| Quality signal | 45/100 · Fair | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | HA_URLHA_TOKEN | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,526 |
| Directory activity | 3 views 0 installs 0 upvotes | 51 views 0 installs 0 upvotes |
| Tools | 19 | 16 |
| Full listing | View MCP Homeassistant | View Git |
Tools & capabilities
MCP Homeassistant tools 19
get_api_statusCheck if the API is runningget_configGet HA configurationget_componentsList loaded componentsget_eventsList event types and listener countsget_servicesList available services by domainget_statesGet all entity statesget_stateGet a specific entity stateset_stateUpdate or create an entity statedelete_stateDelete an entity statefire_eventFire a custom eventcall_serviceCall a Home Assistant servicerender_templateRender a Jinja template- +7 more on the listing page
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_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.
MCP Homeassistant
{
"mcpServers": {
"mcp-homeassistant": {
"command": "uvx",
"args": [
"mcp-homeassistant"
],
"env": {
"HA_URL": "YOUR_HA_URL_HERE",
"HA_TOKEN": "YOUR_HA_TOKEN_HERE"
}
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
MCP Homeassistant is categorized under Home Automation and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick MCP Homeassistant 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.
MCP Homeassistant has no declared pricing — check the project's own site. 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 mcp-homeassistant and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Homeassistant has a quality signal of 45/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 51 views, 0 installs and 91,526 GitHub stars.