mcp-server-surepetcare
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Interface to listen on in HTTP mode; the Docker image sets 0.0.0.0. | 127.0.0.1 |
| MCP_PORT | No | Port to listen on in HTTP mode. | 3000 |
| MCP_TRANSPORT | No | Set to 'http' to run in HTTP mode instead of stdio (alternative to the --http flag). | |
| MCP_PUBLIC_URL | No | Required in HTTP mode. The https:// URL claude.ai reaches the server on. | |
| MCP_STATE_FILE | No | File for registered clients and refresh-token hashes so Claude stays connected across restarts. | ~/.mcp-server-surepetcare/oauth-state.json |
| SUREPETCARE_EMAIL | Yes | Your SurePetcare account email address. | |
| MCP_OWNER_PASSWORD | No | Required in HTTP mode. Passphrase for authorizing Claude; at least 12 characters. | |
| SUREPETCARE_PASSWORD | Yes | Your SurePetcare account password. | |
| SUREPETCARE_DEVICE_ID | No | Optional stable UUID for the device; auto-generated if omitted. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_petsA | List all pets and their current locations (inside or outside) |
| get_pet_detailsC | Get raw pet data including microchip tag information |
| list_devicesA | List all SurePetcare devices, including live lock state and curfew schedule |
| set_lock_stateC | Set the lock state of a SureFlap cat flap |
| rename_deviceA | Rename a SurePetcare device (e.g. a cat flap). Automatically re-asserts any explicit lock override (0-3) that was active beforehand, since the underlying rename endpoint has been observed to silently reset it to unlocked otherwise. |
| set_pet_locationA | Manually mark a pet as inside or outside. Useful when a pet was let through a door other than the flap, so its chip was never read and the app's tracked location is stale. |
| set_led_modeC | Set the hub's LED ring brightness |
| get_pet_reportA | Get aggregated inside/outside activity stats for a pet over a date range - the same data backing the app's activity view. Omitting fromDate/toDate returns the API's default range; per the underlying report endpoint's own warning, an unbounded query can return a very large response, so prefer passing an explicit range. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: pet listing/detail/reporting, device listing, lock control, renaming, manual pet location, and LED brightness. The only near-neighbors are list_pets and get_pet_details, but their descriptions separate current location overview from raw chip/tag data. No two tools appear interchangeable.
All tool names use consistent snake_case with a predictable verb_noun pattern: list_pets, get_pet_details, list_devices, set_lock_state, rename_device, set_pet_location, set_led_mode, get_pet_report. The verbs are standard and the noun targets are clear.
Eight tools is a well-scoped set for a SurePetcare integration covering pets, devices, lock state, location correction, LED control, and activity reporting. Each tool has a distinct role and no obvious filler.
The surface covers core pet tracking and device control workflows, including the important rename/lock-state interaction. Minor gaps remain, such as setting curfew schedules or managing pets beyond reading details, but core CRUD-like operations for the apparent domain are mostly present.