Rachio MCP vs Next Devtools MCP

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

Rachio MCP logoRachio MCPHome Automation · Local subprocess (stdio)MCP server for Rachio sprinkler controllers — schedules, zones, and live watering control52GoodAuth: not declaredNext Devtools MCP logoNext Devtools MCPDeveloper Tools · Local subprocess (stdio)Official Next.js MCP server for coding agents. Provides runtime diagnostics, route inspection, dev server logs, docs search, and upgrade guides. Requires Next.js 16+ dev server for full runtime features.86ExcellentAuth: no auth required

Verdict: choose Rachio MCP for home automation work as a local process; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Rachio MCP logoChoose Rachio MCP when

  • You need dedicated capabilities in the Home Automation domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: RACHIO_ACCESS_TOKEN.
  • You want tools like list_devices, get_device, list_zones.
Explore Rachio MCP

Next Devtools MCP logoChoose Next Devtools MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like nextjs_index, nextjs_call, nextjs_docs.
Explore Next Devtools MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRachio MCP logoRachio MCPNext Devtools MCP logoNext Devtools MCP
CategoryHome AutomationDeveloper Tools
Quality signal52/100 · Good86/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsRACHIO_ACCESS_TOKENNone listed
Verified ownerCommunity listing Verified
GitHub stars7832
Directory activity 2 views 0 installs 0 upvotes 9 views 0 installs 1 upvotes
Tools244

Tools & capabilities

Rachio MCP tools 24

  • list_devicesEvery device on the account — controllers, sensors, weather stations
  • get_deviceFull details + live state for a single device
  • list_zonesZones configured on a controller, with agronomic metadata
  • get_zoneFull detail for a single zone
  • get_calendarScheduled runs + skip events for a date range
  • get_run_historyObserved recent/past zone-run telemetry plus calendar context
  • get_active_alertsUnresolved alerts on a device or zone
  • get_weatherObserved + forecast weather readings for a location
  • list_schedulesFilter by device, location, zone, or schedule id
  • get_scheduleSingle schedule + its locations/devices
  • preview_scheduleDry-run** — returns the Schedule that `create_schedule` would produce, including the server-generated human-readable summary. Never persists
  • create_scheduleCreate a new schedule
  • +12 more on the listing page

Next Devtools MCP tools 4

  • nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.
  • nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).
  • nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.
  • browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.

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.

Rachio MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "rachio-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "rachio-mcp",
        "rachio-mcp-token"
      ],
      "env": {
        "RACHIO_ACCESS_TOKEN": "YOUR_RACHIO_ACCESS_TOKEN_HERE"
      }
    }
  }
}

Next Devtools MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vercel-next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Rachio MCP is categorized under Home Automation and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Rachio MCP for home automation work and Next Devtools MCP for developer tools.

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.

Rachio MCP has no declared pricing — check the project's own site. Next Devtools MCP 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 rachio-mcp and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Rachio MCP has a quality signal of 52/100 (Good) with 2 views, 0 installs and 7 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.