Homeassistant MCP vs Hindsight

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

Homeassistant MCP logoHomeassistant MCPHome AutomationAccess Home Assistant data and control devices (lights, switches, thermostats, etc).40FairAuth: api key requiredHindsight 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 Homeassistant MCP for home automation work; 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?

Homeassistant MCP logoChoose Homeassistant 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: HASS_HOST, HASS_TOKEN, HASS_SOCKET_URL.
Explore Homeassistant MCP

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.
Explore Hindsight

Feature & specification comparison

Rows where the two servers differ are marked.

SpecHomeassistant MCP logoHomeassistant MCPHindsight logoHindsight
CategoryHome AutomationKnowledge & Memory
Quality signal40/100 · Fair57/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthAPI key requiredAPI key required
PricingFreeFree
Required env varsHASS_HOSTHASS_TOKENHASS_SOCKET_URLHINDSIGHT_API_LLM_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars57651,891
Directory activity 6 views 0 installs 0 upvotes 13 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Homeassistant MCP tools

No tool names declared yet. Check the project README from 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.

Homeassistant MCP

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

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"
      }
    }
  }
}

Frequently asked questions

Homeassistant MCP is categorized under Home Automation and uses an install path we have not confirmed yet. Hindsight belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Homeassistant MCP 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. Homeassistant MCP has no confirmed install command yet — follow its own setup instructions.

Homeassistant MCP is listed as free. Auth: api key required. 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 tevonsb-homeassistant-mcp and vectorize-io-hindsight as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Homeassistant MCP has a quality signal of 40/100 (Fair) with 6 views, 0 installs and 576 GitHub stars. Hindsight has 57/100 (Good) with 13 views, 0 installs and 51,891 GitHub stars.