MCP Homeassistant vs Hindsight

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

MCP Homeassistant logoMCP HomeassistantHome Automation · Local subprocess (stdio)MCP server exposing Home Assistant REST API functionality45FairAuth: not declaredHindsight logoHindsightKnowledge & Memory · Local subprocess (stdio)Hindsight: Agent Memory That Works Like Human Memory - Built for AI Agents to manage Long Term Memory57GoodAuth: api key required

Verdict: choose MCP Homeassistant for home automation work as a local process; choose Hindsight for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

MCP Homeassistant logoChoose 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.
Explore MCP Homeassistant

Hindsight logoChoose Hindsight when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: HINDSIGHT_API_LLM_API_KEY, HINDSIGHT_API_LLM_PROVIDER, HINDSIGHT_DB_PASSWORD.
Explore Hindsight

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Homeassistant logoMCP HomeassistantHindsight logoHindsight
CategoryHome AutomationKnowledge & Memory
Quality signal45/100 · Fair57/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsHA_URLHA_TOKENHINDSIGHT_API_LLM_API_KEYHINDSIGHT_API_LLM_PROVIDERHINDSIGHT_DB_PASSWORD
Verified ownerCommunity listingCommunity listing
GitHub stars053,153
Directory activity 3 views 0 installs 0 upvotes 14 views 0 installs 0 upvotes
Tools19Not listed

Tools & capabilities

MCP Homeassistant tools 19

  • get_api_statusCheck if the API is running
  • get_configGet HA configuration
  • get_componentsList loaded components
  • get_eventsList event types and listener counts
  • get_servicesList available services by domain
  • get_statesGet all entity states
  • get_stateGet a specific entity state
  • set_stateUpdate or create an entity state
  • delete_stateDelete an entity state
  • fire_eventFire a custom event
  • call_serviceCall a Home Assistant service
  • render_templateRender a Jinja template
  • +7 more on the listing page

Hindsight tools

No tool names declared yet. Check the project README from 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-homeassistant": {
      "command": "uvx",
      "args": [
        "mcp-homeassistant"
      ],
      "env": {
        "HA_URL": "YOUR_HA_URL_HERE",
        "HA_TOKEN": "YOUR_HA_TOKEN_HERE"
      }
    }
  }
}

Hindsight

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vectorize-io-hindsight": {
      "command": "npx",
      "args": [
        "-y",
        "@vectorize-io/hindsight-coding-agents"
      ],
      "env": {
        "HINDSIGHT_API_LLM_API_KEY": "YOUR_HINDSIGHT_API_LLM_API_KEY_HERE",
        "HINDSIGHT_API_LLM_PROVIDER": "YOUR_HINDSIGHT_API_LLM_PROVIDER_HERE",
        "HINDSIGHT_DB_PASSWORD": "YOUR_HINDSIGHT_DB_PASSWORD_HERE"
      }
    }
  }
}

Frequently asked questions

MCP Homeassistant is categorized under Home Automation and uses a local stdio subprocess. Hindsight belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MCP Homeassistant for home automation work and Hindsight for knowledge & memory.

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. Hindsight is listed as free. Auth: api key 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 vectorize-io-hindsight 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. Hindsight has 57/100 (Good) with 14 views, 0 installs and 53,153 GitHub stars.