Skip to main content
📖 The AI Tool Bible

Cloudflare MCP Server vs Home Assistant MCP

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

 Cloudflare MCP Server logo
Cloudflare MCP Server
MCP Servers
Home Assistant MCP logo
Home Assistant MCP
MCP Servers
TaglineOfficial suite of remote MCP servers that let Claude, Cursor, and other agents read and control your Cloudflare account.Open-source MCP server that lets any LLM control and observe a Home Assistant smart home in real time.
CategoryMCP ServersMCP Servers
PricingFreemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/monthFree· Free and open source (Apache 2.0). Self-hosted; only cost is your own Home Assistant instance and the LLM client you connect to it.
Model——
Editorial score——
Use cases
Debugging Workers with live logs from chatDeploying and configuring Workers bindingsGrounded Q&A over Cloudflare developer docsQuerying Radar for real-time internet traffic dataPulling audit logs for compliance answersRunning a headless browser via Browser RenderingAutoRAG pipelines against R2-hosted corporaReviewing Cloudflare One CASB findingsDNS analytics and Logpush inspectionBuilding custom MCP servers from the Demo Day template
Conversational smart-home control from Claude Desktop or CursorLLM-driven Home Assistant automationsReal-time device state monitoring via SSEVoice-agent frontends that call HA servicesBulk add-on and HACS package management through chatPrototyping custom home-lab AI assistantsNatural-language climate and lighting scenesCamera snapshot and motion event triaging
Pros
  • Official, first-party servers maintained by Cloudflare with 4k+ GitHub stars and active development.
  • Remote-hosted at stable URLs so most clients need only a URL and OAuth login, no local install.
  • Split into 16 focused servers so agents get relevant tools without prompt bloat.
  • Covers most of the Cloudflare platform: Workers, R2, KV, D1, Radar, DNS analytics, AI Gateway, AutoRAG, Browser Rendering, audit logs, CASB.
  • Works with any MCP-capable client - Claude Desktop, Claude Code, Cursor, Windsurf, and OpenAI Responses API.
  • Apache 2.0 source is on GitHub, so teams can self-host, audit, or extend any server.
  • Docs AI Search server gives agents grounded answers over the full developers.cloudflare.com corpus.
  • Broad domain coverage — lights, climate, covers, media, locks, vacuums, cameras, and more mapped to MCP tools out of the box
  • Real-time SSE subscriptions let an LLM react to state changes and automation triggers, not just poll
  • Docker Compose setup and clear env-var config make it easy to run alongside an existing Home Assistant install
  • Exposes system-level surfaces most HA wrappers skip: add-on management, HACS package installs, automation CRUD
  • Token auth plus rate limiting on the bridge, so it isn't a trivially open control plane
  • Apache 2.0 licensed, TypeScript, 500+ GitHub stars and active commits — reasonable community traction for an MCP project
Cons
  • Only useful if you already run on Cloudflare - it is not a general cloud MCP.
  • Advanced capabilities inherit Cloudflare paywalls (Browser Rendering, AutoRAG, CASB, Cloudflare One all require paid plans).
  • Write-capable tools mean a compromised or over-permissioned token can push destructive changes; scoping API tokens carefully is on you.
  • Because the servers are hosted by Cloudflare, your agent's queries and returned data traverse Cloudflare infrastructure - not ideal for teams that want everything to stay in-VPC.
  • OAuth and remote-MCP support is still uneven across MCP clients, so setup varies and some clients need a manual token instead.
  • Sixteen separate endpoints can be confusing - discovery of which server owns which capability is not always obvious from client-side.
  • Requires a working Home Assistant instance and long-lived access token — not useful without one
  • Self-hosted only; you own the reverse-proxy, TLS, and network exposure decisions
  • Model-agnostic by design, so quality of device control depends heavily on which LLM client you attach
  • Single-maintainer community project — issue triage and roadmap can be slower than vendor MCP servers
  • Broad tool surface can flood an LLM's context window if you don't scope subscriptions to specific domains
Websitegithub.comgithub.com
Pick Cloudflare MCP Server if
  • ✅ Official, first-party servers maintained by Cloudflare with 4k+ GitHub stars and active development.
  • ✅ Remote-hosted at stable URLs so most clients need only a URL and OAuth login, no local install.
  • ✅ Split into 16 focused servers so agents get relevant tools without prompt bloat.
  • ✅ Covers most of the Cloudflare platform: Workers, R2, KV, D1, Radar, DNS analytics, AI Gateway, AutoRAG, Browser Rendering, audit logs, CASB.
Pick Home Assistant MCP if
  • ✅ Broad domain coverage — lights, climate, covers, media, locks, vacuums, cameras, and more mapped to MCP tools out of the box
  • ✅ Real-time SSE subscriptions let an LLM react to state changes and automation triggers, not just poll
  • ✅ Docker Compose setup and clear env-var config make it easy to run alongside an existing Home Assistant install
  • ✅ Exposes system-level surfaces most HA wrappers skip: add-on management, HACS package installs, automation CRUD
Compare a different pair →