Litter-Robot MCP Server

Community

Monitor and control Whisker-connected pet devices using natural language.

How to install ↓ Compare GitHub source repository ↗

Category: Other #168 of 230
Stars: ★ 198 Very popular
Transport: stdio (local process)
Runtime: Python
Credentials: API key / credential required
License: MIT
Last commit: 7 days ago
Tools: 24

47FMRS · D

This community-maintained, unofficial pylitterbot MCP server provides status queries, activity analysis, settings management, and selected controls for Whisker devices. The README explicitly identifies the API as experimental and warns about plaintext credential storage.

Strongest · Documentation 12/20 Weakest · Reliability 7/20

Reliability

7/20

Security and permissions

9/20

Maintenance

8/20

Documentation

12/20

Setup experience

11/20

Why each score

Reliability 7/20: The README provides MCP installation, launch commands, and tool categories, but there is no manifest, source code, tests, CI, or evidence of the initialization/tool-list handshake. Declared tools and runtime behavior therefore cannot be verified, and error handling and dependency controllability are undocumented. Static review warrants a deduction.
Security and permissions 9/20: The documentation clearly requires Whisker account credentials and warns that configuration stores them in plaintext, with file-permission guidance. However, the server accesses an external Whisker API and exposes side-effecting operations such as cleaning, resetting, feeding, and changing settings. There is no source evidence of least privilege, per-tool authorization, confirmation, data boundaries, or network-flow controls, so points are deducted; no listed red-line risk is demonstrated.
Maintenance 8/20: The repository is not archived, declares an MIT license, and identifies maintainer support channels. However, the supplied evidence contains no release history, commit activity, dependency-update process, test status, or security-response channel. The popularity figures are discovery signals only, so maintenance receives a modest score.
Documentation 12/20: The README covers purpose, supported devices, installation, authentication examples, launch methods, client configuration, tool names, and experimental reverse-engineering limitations. It lacks complete tool parameters, permission behavior, failure handling, compatibility guidance, and troubleshooting details; the MCP manifest is also unavailable, so capabilities cannot be checked.
Setup experience 11/20: The README gives pip installation, an optional MCP extra, module launch commands, and a Claude Desktop configuration example, making the path reasonably clear. It still requires manual Python environment preparation and credential configuration, with no platform matrix, dependency versions, authentication-failure guidance, or verifiable end-to-end setup evidence, so points are deducted.

Static review · not runListed 2026-08-14

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

Users with supported Whisker devices who want natural-language management through Claude Desktop.
Households that need to monitor or manage multiple Litter-Robot or Feeder-Robot devices.

Not for

Users who require an official Whisker API or an officially maintained server.
Devices or features not listed as supported in the README, including Litter-Robot 5 cameras.
Users unwilling to provide Whisker account credentials or accept experimental API risk.

Required permissions

Requires the Whisker account username and password.
Requires access to robots associated with the account, including their status, activity, pet, and settings data.
Control tools may start cleaning, reset devices, dispense snacks, or change device settings.

Risks and side effects

The API is unofficial and experimental, reverse-engineered from network traffic and the Whisker app; it may stop working at any time.
The Claude Desktop example stores credentials in plaintext, so weak file permissions could expose them.
Control tools operate real pet devices; verify the target robot and requested action before execution.

Setup

Before you start

Runtime：Python

LITTER_ROBOT_USERNAME required The email address of your Whisker account, the same one used in the Whisker app.

LITTER_ROBOT_PASSWORD requiredsecret Your Whisker account password; it is stored in plaintext in the config, so keep the file permissions owner-only.

Install the MCP extra with pip install pylitterbot[mcp]. Run pylitterbot-mcp, or run python -m pylitterbot.mcp. In Claude Desktop, use the supplied configuration example and set LITTER_ROBOT_USERNAME and LITTER_ROBOT_PASSWORD. Restrict the configuration file to owner-only read/write access and do not commit it to version control.

claude_desktop_config.json

{"mcpServers":{"litter-robot":{"command":"python","args":["-m","pylitterbot.mcp"],"env":{"LITTER_ROBOT_USERNAME":"[email protected]","LITTER_ROBOT_PASSWORD":"your_password"}}}}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "litter-robot": {
      "command": "python",
      "args": [
        "-m",
        "pylitterbot.mcp"
      ],
      "env": {
        "LITTER_ROBOT_USERNAME": "[email protected]",
        "LITTER_ROBOT_PASSWORD": "your_password"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add litter-robot -e [email protected] -e LITTER_ROBOT_PASSWORD=your_password -- python -m pylitterbot.mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After installing pylitterbot[mcp] and configuring Claude Desktop, restart the client and confirm tools like get_robots and fleet_overview appear in the tool list; asking "list my robots" and getting Whisker device names back proves the connection works.

Troubleshooting

Verify that pylitterbot[mcp] is installed rather than only the base package.
Verify that the server is started with pylitterbot-mcp or python -m pylitterbot.mcp.
Verify that LITTER_ROBOT_USERNAME and LITTER_ROBOT_PASSWORD are correct and available to the process.
Verify the Claude Desktop command, arguments, and JSON configuration.
Verify that the device is a listed supported model, and remember that the reverse-engineered API may have changed or stopped working.

Things to try

Once connected, you can ask your AI assistant things like:

List all my robots and show their current status
Start a cleaning cycle on any litter box that is READY
Give me a maintenance forecast for all robots so I know which one needs emptying soon
Set the night light brightness of my Litter-Robot to 50

Tools 24

get_robots read-only

List robots associated with the account.

get_robot_status read-only

Retrieve a robot's status.

get_activity_history read-only

Retrieve activity history.

get_insight read-only

Retrieve robot insight data.

get_pets read-only

Retrieve pet information.

start_cleaning writes

Start a cleaning cycle.

reset_robot writes

Reset a robot.

give_snack writes

Dispense a snack to a pet.

Show 16 more tools

set_power_status writes

Set the power status.

set_name writes

Set the robot name.

set_night_light writes

Configure the night light.

set_night_light_brightness writes

Set night-light brightness.

set_night_light_mode writes

Set the night-light mode.

set_panel_lockout writes

Configure panel lockout.

set_wait_time writes

Set the wait time.

set_sleep_mode writes

Set sleep mode.

fleet_overview read-only

Provide prioritized status and alerts across all robots.

clean_all_ready writes

Start cleaning on all robots in READY state.

sync_settings writes

Copy one robot's settings to others of the same model.

pet_usage_report read-only

Summarize activity data across robots with pet information.

maintenance_forecast read-only

Estimate when each robot needs emptying.

household_digest read-only

Summarize household activity within a time range.

troubleshooting_report read-only

Create a diagnostic bundle for a robot, including errors.

robot_comparison read-only

Compare settings and metrics across robots.

Use cases

Check the status of one or more connected robots.

Start cleaning, reset a robot, or dispense a snack using natural language.

Manage night-light, sleep-mode, wait-time, and panel-lockout settings.

Review activity, pet usage, maintenance forecasts, and troubleshooting data.

Supported clients

Claude Desktop

Listed from the project's documentation, not tested by this site.

Overview

The Litter-Robot MCP Server is an optional MCP server included with pylitterbot. It lets AI assistants monitor and control Whisker connected self-cleaning litter boxes and feeders through natural language. The README lists support for Litter-Robot 3 with Connect, Litter-Robot 4, and Feeder-Robot.

Similar servers

Hevy MCP 77 · B

Manage your Hevy workout data from AI assistants via MCP.

★ 517 · Tools 26 Compare with this →

Firecrawl MCP Server 75 · B

Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents

★ 7.6k · Tools 11 Compare with this →

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 659 · Tools 11 Compare with this →

Compartment 75 · B

Encrypted, fully offline long-term memory for AI agents

★ 583 · Tools 14 Compare with this →

Compare with other MCP servers

Source revision c9377089e5b7 Data synced 2026-10-19 Read the FMRS scoring method