pickuppatrol-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PICKUPPATROL_PASSWORD | Yes | Your PickUp Patrol account password. | |
| PICKUPPATROL_USERNAME | Yes | Your PickUp Patrol account email address. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pup_get_sessionA | The signed-in PickUp Patrol parent account: name, email, last sign-in, and the students linked to it. Start here to discover student and school ids. |
| pup_list_studentsA | Every student on the account, each with their weekly default dismissal plan and whether those defaults still need a parent review. |
| pup_get_studentA | One student in full, including the default dismissal plan for each weekday. Pass raw: true for the untouched API record. |
| pup_healthcheckA | Verify the configured credentials sign in and the PickUp Patrol API answers. Reports the server version, the students the account can see, and — when it fails — an error.kind saying which hop broke: no_credential (nothing configured), credential_rejected (PickUp Patrol refused the username/password), verification_pending (a two-factor account), edge_blocked (a CDN/WAF refused the request before PickUp Patrol saw it, so the credentials were never judged), timeout, transport or http. Read-only; never returns the credentials. |
| pup_list_transportationsA | The dismissal options a school offers (bus, car pickup, walker, absent …) with the rules each one imposes: whether a note is required, whether it takes a car number, whether it is an early dismissal, and the daily cutoff time. Read this before setting a plan. |
| pup_get_schoolA | A school profile together with its per-weekday notify times and plan cutoff times, and the settings that decide whether parents may set plans at all. |
| pup_list_non_school_daysA | Dates a plan cannot be set for at a school (holidays, closures, weekends), and optionally the dates in a range that already differ from the student defaults. |
| pup_list_car_numbersA | The car numbers a school has issued to this account, for dismissal options where usesCarNumbers is true. |
| pup_list_plansA | Day-by-day dismissal plans across a date range for every student on the account, as PickUp Patrol returns them. |
| pup_get_planA | The dismissal plan for one student on one date — the option in force, any note, the early-dismissal time, and whether the date is locked because the cutoff has passed. |
| pup_set_planA | Change how a student is dismissed on one or more specific dates, or clear those dates back to the student's weekly default. This changes how a child actually leaves school. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The preview shows the exact payload. Read pup_list_transportations first — options differ in whether they require a note, a car number or an early-dismissal time. |
| pup_get_default_plansA | A student's weekly default dismissal plan — how they normally leave school on each day of the week — and whether the defaults still need a parent review. |
| pup_set_default_plansA | Change a student's weekly default dismissal plan for one or more weekdays, or clear every default. This is how the child leaves school on any date without a specific plan. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Read pup_list_transportations first. |
| pup_mark_defaults_reviewedA | Mark a student's default plans as reviewed, clearing the school's 'needs review' prompt. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). |
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 14 tools
Tools separate reads (list/get) from writes (set/mark) and cover distinct resources (students, plans, schools, transportations, car numbers). Minor overlap exists: pup_get_student and pup_get_default_plans both expose default plans, and pup_list_students vs pup_get_session both list students, but descriptions clarify scope.
All tools use the pup_ prefix and mostly follow a verb_noun pattern (list/get/set/mark). pup_healthcheck is the lone noun-style outlier, but the overall convention remains predictable and readable.
14 tools is well within the ideal range and each maps to a clear operation in the dismissal-planning domain. No redundant or trivial tools inflate the set.
Reads, writes, clears, and review-status operations cover the full plan lifecycle for students across dates, defaults, schools, transportations, and non-school days. Discovery paths (session/students) provide the IDs needed for deeper calls, leaving no obvious dead ends.