Unofficial MCP server for PetKit smart feeders: status, feeding history and schedule control.
MCP (Model Context Protocol) server for the PetKit cloud API. Exposes feeder status and control for the Fresh Element Solo (device type D4) as MCP tools.
Disclaimer: This project is not affiliated with, endorsed by, or in any way associated with PetKit. It is an independent, community-developed integration created by a happy user of their hardware and software. PetKit and Fresh Element Solo are trademarks of their respective owner. Use of this package is at your own risk. The underlying API is unofficial and reverse-engineered by the community - it may change or break without notice.
| Tool | Description |
|---|---|
list_feeders | List all Fresh Element Solo feeders and their live state (food/battery/desiccant status, lock/light/sound settings, today's feed totals) |
feed_now | Dispense food immediately |
update_feeder_setting | Change a numeric setting (child lock, indicator light, dispense tone, shortage alarm, ...) |
skip_scheduled_feed | Skip one of today's scheduled meals (d4/removeDailyFeed), leaving the recurring plan untouched |
restore_scheduled_feed | Undo a skip for today (d4/restoreDailyFeed) |
The D4 only accepts these five portion sizes: 10, 20, 30, 40, 50.
list_feeders also returns feedPlanToday: today's scheduled meals from the feeder's weekly plan (d4/device_detail's multiFeedItem), each with its readable time, the feedTime (seconds since midnight) that skip_scheduled_feed takes, the portion amount in feed_now's units, and the meal name.
list_feeders' fedToday/fedTodayScheduled/fedTodayExtra/fedTodayPlanned/dispensesToday/feedTimesToday fields reflect what each physical feeder dispensed - PetKit has no way to attribute a dispense to a specific cat. If your cats share or steal from each other's bowls, these numbers won't tell you what any one cat actually ate.
| Key | Meaning |
|---|---|
manualLock | Child lock (0/1) |
lightMode | Indicator light |
feedSound | Dispense tone (0/1) |
foodWarn | Shortage alarm (0/1) |
Other numeric keys the device reports via list_feeders may also work but are unconfirmed.
Set the following environment variables before starting the server:
export PETKIT_EMAIL="your@email.com"
export PETKIT_PASSWORD="yourpassword"
export PETKIT_REGION="Netherlands" # must match the exact region name shown in the PetKit app
export PETKIT_TIMEZONE="Europe/Amsterdam" # optional, defaults to the host's own timezone
Note: PetKit account passwords are capped at 6-14 characters. A longer password fails login with a generic "incorrect username or password" error indistinguishable from an actually-wrong one - if login fails unexpectedly, check that first.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"petkit": {
"command": "npx",
"args": ["mcp-server-petkit"],
"env": {
"PETKIT_EMAIL": "your@email.com",
"PETKIT_PASSWORD": "yourpassword",
"PETKIT_REGION": "Netherlands"
}
}
}
}
To use the server from claude.ai and the Claude mobile apps, run it in HTTP mode on an
always-on machine and add it as a custom connector. claude.ai connects from the
internet, so the server needs a public https:// URL - a Cloudflare Tunnel or
Tailscale Funnel gives you one without opening ports on your router.
HTTP mode is single-user: when you connect Claude, the server shows a page asking for your owner passphrase. Anyone who knows it can authorize a client, and anyone with a token can dispense food or change the feeding plan - pick a strong one.
npx mcp-server-petkit --http # or MCP_TRANSPORT=http
| Variable | Default | |
|---|---|---|
MCP_PUBLIC_URL | (required) | The https:// URL claude.ai reaches the server on |
MCP_OWNER_PASSWORD | (required) | Passphrase for authorizing Claude, at least 12 characters |
MCP_HOST | 127.0.0.1 | Interface to listen on; the Docker image sets 0.0.0.0 |
MCP_PORT | 3000 | |
MCP_STATE_FILE | ~/.mcp-server-petkit/oauth-state.json | Registered clients and refresh-token hashes, so Claude stays connected across restarts |
plus the PETKIT_* variables from Configuration.
Each release publishes ghcr.io/dirkjanfaber/mcp-server-petkit for amd64 and arm64,
tagged with the version and latest. With a Cloudflare Tunnel alongside it, no port
needs publishing: create a tunnel in the Cloudflare dashboard, point its public
hostname at http://petkit-mcp:3000, and put its token in .env next to the PetKit
and MCP_* settings:
# docker-compose.yml
services:
petkit-mcp:
image: ghcr.io/dirkjanfaber/mcp-server-petkit:latest # or pin a version, e.g. :0.3.0
restart: unless-stopped
env_file: .env # PETKIT_*, MCP_PUBLIC_URL, MCP_OWNER_PASSWORD
volumes:
- petkit-data:/data
cloudflared:
image: cloudflare/cloudflared:latest
command: tunnel run
restart: unless-stopped
environment:
TUNNEL_TOKEN: ${TUNNEL_TOKEN}
volumes:
petkit-data:
Update with docker compose pull && docker compose up -d. To build the image yourself
instead, replace image: with build: https://github.com/dirkjanfaber/mcp-server-petkit.git.
The server trusts one proxy hop (X-Forwarded-For from cloudflared) for rate limiting.
Don't also publish its port directly to the internet.
In claude.ai: Settings → Connectors → Add custom connector, with URL
https://<your public host>/mcp. Claude registers itself, opens the passphrase page,
and once you allow it, the tools show up in claude.ai and the mobile apps.
PetKit allows one session per account. The server's login signs the PetKit app out (and vice versa); it re-logs in on its own when that happens, but expect the app to ask you to log in again whenever the server restarts or its session lapses. Running the stdio server, Node-RED's PetKit nodes, or a second HTTP instance on the same account makes them take turns signing each other out.
node-red-contrib-petkit's CLAUDE.mdSource-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y mcp-server-petkitMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-dirkjanfaber-mcp-server-petkit": {
"command": "npx",
"args": [
"-y",
"mcp-server-petkit"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencemcp-server-petkitnpmPetKit works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.