SurePetcare

mcp-server-surepetcare

MCP (Model Context Protocol) server for the SurePetcare cloud API. Exposes pet location monitoring, SureFlap lock control, device renaming, and hub LED control as MCP tools.

Disclaimer: This project is not affiliated with, endorsed by, or in any way associated with Sure Petcare Ltd. It is an independent, community-developed integration created by happy users of their hardware and software. SurePetcare, SureFlap, and SureFeed are trademarks of Sure Petcare Ltd. 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.

Tools

Lock state values

LED mode values

Configuration

Set the following environment variables before starting the server:

export SUREPETCARE_EMAIL="your@email.com"

export SUREPETCARE_PASSWORD="yourpassword" export SUREPETCARE_DEVICE_ID="stable-uuid" # optional, auto-generated if omitted

Usage with Claude Desktop

Add to your claude_desktop_config.json:

{

"mcpServers": { "surepetcare": { "command": "npx", "args": ["mcp-server-surepetcare"], "env": { "SUREPETCARE_EMAIL": "your@email.com", "SUREPETCARE_PASSWORD": "yourpassword" } } } }

Remote use: claude.ai connector (HTTP + OAuth)

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. Private overlay networks such as ZeroTier or plain Tailscale aren't enough: claude.ai connects from Anthropic's servers, not from your devices.

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 unlock your cat flap - pick a strong one.

npx mcp-server-surepetcare --http   # or MCP_TRANSPORT=http

plus the SUREPETCARE_* variables from Configuration. Set SUREPETCARE_DEVICE_ID to a fixed UUID, or every restart looks like a new device logging in.

Docker (e.g. on a Raspberry Pi)

Each release publishes ghcr.io/dirkjanfaber/mcp-server-surepetcare for amd64, arm64 and arm/v7 (32-bit Raspberry Pi OS), tagged with the version and latest. Publish its port on loopback only, so the tunnel is the only way in:

# docker-compose.yml

services: surepetcare-mcp: image: ghcr.io/dirkjanfaber/mcp-server-surepetcare:latest # or pin a version restart: unless-stopped env_file: .env # SUREPETCARE_*, MCP_PUBLIC_URL, MCP_OWNER_PASSWORD ports:

• "127.0.0.1:3200:3000" volumes:
• surepetcare-data:/data

volumes: surepetcare-data:

With Tailscale Funnel (no domain needed), run sudo tailscale funnel --bg 3200 and use the URL tailscale funnel status shows as MCP_PUBLIC_URL.

claude.ai only connects on port 443, so Funnel's other ports (8443, 10000) don't work for a connector. If the machine's own name is already taken by another server, give this one its own tailnet machine with a Tailscale container next to it. Drop the ports: mapping above, set MCP_PUBLIC_URL to https://surepet. .ts.net, and add:

  surepetcare-tailscale:

image: tailscale/tailscale:latest hostname: surepet restart: unless-stopped environment: TS_HOSTNAME: surepet TS_AUTHKEY: ${TS_AUTHKEY} # only used for the first login TS_STATE_DIR: /var/lib/tailscale TS_SERVE_CONFIG: /config/serve.json TS_USERSPACE: "true" volumes:

• surepetcare-tailscale:/var/lib/tailscale
• ./surepet-ts:/config:ro

with surepetcare-tailscale: added under volumes:, and surepet-ts/serve.json:

{

"TCP": { "443": { "HTTPS": true } }, "Web": { "${TS_CERT_DOMAIN}:443": { "Handlers": { "/": { "Proxy": "http://surepetcare-mcp:3000" } } } }, "AllowFunnel": { "${TS_CERT_DOMAIN}:443": true } }

Generate the auth key in the Tailscale admin console under Settings → Keys. Without one, the container prints a login link that expires after about a minute. Once logged in, the machine stays logged in through the volume and the key can be removed.

With a Cloudflare Tunnel (needs a domain on Cloudflare), point a public hostname at the server instead. Don't put Cloudflare Access in front of it: claude.ai can't get past its login page.

Check the public URL before connecting Claude:

curl https://<your public host>/.well-known/oauth-authorization-server

It should return JSON whose issuer matches MCP_PUBLIC_URL.

Update with docker compose pull && docker compose up -d. The server trusts one proxy hop (X-Forwarded-For from the tunnel in front of it) for rate limiting. Don't also publish its port directly to the internet.

Connecting Claude

In claude.ai: Settings → Connectors → Add custom connector, with URL https:// /mcp. Claude registers itself, opens the passphrase page, and once you allow it, the tools show up in claude.ai and the mobile apps.

References

• Reverse-engineered API (PHP): https://github.com/alextoft/sureflap
• Python client (surepy): https://github.com/benleb/surepy
• Local MQTT alternative (PetHubLocal): https://github.com/PetHubLocal/pethublocal