apify-mcp-server vs ha-mcp
Two of the top projects in MCP servers, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.
apify-mcp-server
Official MCP server exposing Apify Store Actors as tools for web scraping
ha-mcp
MCP server that lets AI assistants configure and control Home Assistant
Verdict
apify-mcp-server ranks higher, 86 to 80. Of the 4 score parts we measure for both, apify-mcp-server leads on 1, ha-mcp on 1 and 2 are even.
- Adoptionapify-mcp-server leads by 32 points, 73 to 41: a wide gap.
- FreshnessEven at 100.
- Maintenanceha-mcp leads by 15 points, 99 to 84: a wide gap.
- Agent-readyEven at 85.
Pick apify-mcp-server if you are
Agent builders who need web scraping and data extraction tools over MCP
- One connection reaches thousands of Store Actors instead of a separate MCP server per site
- Tool categories selectable via `tools` URL parameter, `--tools` flag or `TOOLS` env var
Pick ha-mcp if you are
Home Assistant users who want MCP clients to manage their smart home
- 87 tools covering automations, dashboards, helpers, areas, backups, traces and device registry
- In-process integration works on OS, Supervised, Container and Core installs
| What we compare | apify-mcp-server | ha-mcp |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 73, popular | 41, known |
| Momentum | Not scored for this kind | Not scored for this kind |
| Freshness | 100, active | 100, active |
| Maintenance | 84, healthy | 99, healthy |
| Agent-ready | 85, ready | 85, ready |
| Facts from GitHub and the README | ||
| Stars | 15.7k | 7.1k |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Nov 2026 | Nov 2026 |
| Last release | Nov 2026 | Nov 2026 |
| Language | TypeScript | Python |
| Docker | Yes | Yes |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Mentioned |
apify-mcp-server
MCP server that lets an agent search Apify Store, read an Actor's input schema and pricing, run it, and fetch results from its dataset. It runs hosted at mcp.apify.com over Streamable HTTP with OAuth or a bearer token, or locally over stdio via the @apify/actors-mcp-server npm package. Actors execute on the Apify platform in both modes.
Who it is for: Agent builders who need web scraping and data extraction tools over MCP
Strengths
- One connection reaches thousands of Store Actors instead of a separate MCP server per site
- Tool categories selectable via `tools` URL parameter, `--tools` flag or `TOOLS` env var
- Hosted OAuth endpoint plus local stdio mode and an .mcpb bundle for supported clients
- Also covers Actor builds, schedules, tasks, storage and Apify API access as opt-in tools
Weaknesses
- Requires an Apify account; Actors run and store results on Apify's platform, not locally
- Actor runs are paid per Actor pricing; cost depends on each Actor
- call-actor waits only 30 seconds by default, up to 45; longer runs need polling
- Local stdio mode lacks inferred output schemas for Actor results
- no GPU
- Docker
- Needs Apify account and API token or OAuth, Apify platform (Actors), Node.js 22+ for local stdio
ha-mcp
ha-mcp exposes 87 tools over the Model Context Protocol so clients such as Claude, ChatGPT and Cursor can search entities, control devices, and create or edit automations, scripts, helpers and dashboards in Home Assistant. It is built on FastMCP and installs as an in-process HACS/Marketplace integration, a Home Assistant app (add-on), Docker, or uvx/PyPI. Safety features include read-only mode, per-tool disabling and automatic edit backups.
Who it is for: Home Assistant users who want MCP clients to manage their smart home
Strengths
- 87 tools covering automations, dashboards, helpers, areas, backups, traces and device registry
- In-process integration works on OS, Supervised, Container and Core installs
- Read Only Mode, per-tool enable/disable and automatic backups before edits
- Setup Wizard generates config for 15+ clients; demo server available to try first
Weaknesses
- Integration requires Home Assistant 2026.8.0 or newer
- Acts with an administrator token; a leaked token or secret URL grants broad access
- stdio transport has known connection problems; README recommends it only for demos
- Several install paths exist; running more than one per client causes connection hangs
- no GPU
- Docker + Compose
- Needs Home Assistant 2026.8.0+, Home Assistant administrator access token, FastMCP
- Models: Claude, ChatGPT, Gemini CLI, Open WebUI, Cursor
- port 9584
More in MCP servers
Building with these?
We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.