← Back to directory
L

Litter-Robot MCP Server

Community
Monitor and control Whisker-connected pet devices using natural language.
GitHub source repository ↗
★ 187 Stars Category · Other Very popular Source revision cfb00741137f
47FMRS · D
Reliability
7/20
Security and permissions
9/20
Maintenance
8/20
Documentation
12/20
Setup experience
11/20

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.

Read the FMRS scoring method →

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.

Tools

get_robots
List robots associated with the account.
get_robot_status
Retrieve a robot's status.
get_activity_history
Retrieve activity history.
get_insight
Retrieve robot insight data.
get_pets
Retrieve pet information.
start_cleaning
Start a cleaning cycle.
reset_robot
Reset a robot.
give_snack
Dispense a snack to a pet.
set_power_status
Set the power status.
set_name
Set the robot name.
set_night_light
Configure the night light.
set_night_light_brightness
Set night-light brightness.
set_night_light_mode
Set the night-light mode.
set_panel_lockout
Configure panel lockout.
set_wait_time
Set the wait time.
set_sleep_mode
Set sleep mode.
fleet_overview
Provide prioritized status and alerts across all robots.
clean_all_ready
Start cleaning on all robots in READY state.
sync_settings
Copy one robot's settings to others of the same model.
pet_usage_report
Summarize activity data across robots with pet information.
maintenance_forecast
Estimate when each robot needs emptying.
household_digest
Summarize household activity within a time range.
troubleshooting_report
Create a diagnostic bundle for a robot, including errors.
robot_comparison
Compare settings and metrics across robots.

Setup

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

Fit and risk

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.

Troubleshooting

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

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 DesktopFull support