care.com CLI: search caregivers, review applicants/messages, analyze and reach out - over your own authenticated session
Learn more at Care.
Created by @beetz12 (david).
Quick Start
1. Install
See Install above.
2. Authenticate
This CLI uses your browser session for authentication. Log in to .care.com in Chrome, then:
care-pp-cli auth login --chrome
Or import an existing browser capture:
care-pp-cli auth login --cookies-file storage-state.json
--cookies-file accepts Playwright storage-state JSON or a raw Cookie: header text file. The Chrome path requires a cookie extraction tool. Install one:
pip install pycookiecheat # Python (recommended)
brew install barnardb/cookies/cookies # Homebrew
When your session expires, run auth login --chrome again.
3. Verify Setup
care-pp-cli doctor
This checks your configuration and credentials.
4. Try Your First Command
care-pp-cli calendars --operation-name GetCalendar
Usage
Run care-pp-cli --help for the full command reference and flag list.
Paths & environment variables
This CLI separates local files into four path kinds:
| Kind | Contents |
|---|
config | User-editable settings such as config.toml and saved profiles |
data | Durable local data: credentials.toml, data.db, cookies, browser-session proof files, and other auth sidecars |
state | Runtime state such as persisted queries, jobs, and teach.log |
cache | Regenerable HTTP/cache files |
Each kind resolves independently. The ladder is:
- Per-kind env var:
CARE_CONFIG_DIR, CARE_DATA_DIR, CARE_STATE_DIR, or CARE_CACHE_DIR
--home <dir> for this invocationCARE_HOME for a flat relocated root- XDG env vars:
XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME
- Platform defaults matching existing installs
For containers and agent sandboxes, prefer a single relocated root:
export CARE_HOME=/srv/care
care-pp-cli doctor
Under CARE_HOME=/srv/care, the four dirs resolve to /srv/care/config, /srv/care/data, /srv/care/state, and /srv/care/cache.
On Windows, set the same variable in PowerShell:
$env:CARE_HOME = "C:\srv\care"
care-pp-cli doctor
Under $env:CARE_HOME = "C:\srv\care", the four dirs resolve to C:\srv\care\config, C:\srv\care\data, C:\srv\care\state, and C:\srv\care\cache.
MCP servers do not receive CLI flags from the host. Put relocation in the host env block:
{
"mcpServers": {
"care": {
"command": "care-pp-mcp",
"env": {
"CARE_HOME": "/srv/care"
}
}
}
}
Precedence matters in fleets: an ambient per-kind variable such as CARE_DATA_DIR overrides an explicit --home for that kind. Use CARE_HOME or the per-kind variables for durable fleet relocation; treat --home as the weaker per-invocation lever.
Relocation is one-way. Unsetting CARE_HOME does not move files back to platform defaults, and doctor cannot find credentials left under a former root. Move the files manually before unsetting relocation variables.
Existing installs keep working because the platform-default rung matches the legacy layout. On the first auth write, stored secrets leave config.toml and are consolidated into credentials.toml under the data directory. Run care-pp-cli doctor --fail-on warn to check path and credential-location warnings in automation.
Commands
availabilities
GraphQL BFF operations for availabilities
care-pp-cli availabilities - Fetch availabilities events
bookings
GraphQL BFF operations for bookings
care-pp-cli bookings request-list-jobs-basic - Fetch bookings request list jobs basiccare-pp-cli bookings request-list-jobs-extended - Fetch bookings request list jobs extended
calendars
GraphQL BFF operations for calendars
care-pp-cli calendars - Fetch calendars
care_jobs
GraphQL BFF operations for jobs
care-pp-cli care-jobs applicant-hired - Fetch jobs applicant hiredcare-pp-cli care-jobs application-interest - Fetch jobs application interestcare-pp-cli care-jobs application-seeker-interest-counts - Fetch jobs application seeker interest countscare-pp-cli care-jobs applications - Fetch jobs applicationscare-pp-cli care-jobs by-seeker-u-u-i-d - Fetch jobs by seeker u u i dcare-pp-cli care-jobs by-seeker-u-u-i-d-applicants - Fetch jobs by seeker u u i d applicantscare-pp-cli care-jobs child-care-one-time-update - Fetch jobs child care one time updatecare-pp-cli care-jobs profile - Fetch jobs profilecare-pp-cli care-jobs setup-c-c - Fetch jobs setup c ccare-pp-cli care-jobs wages - Fetch jobs wagescare-pp-cli care-jobs wages-2 - Fetch jobs wages
caregivers
GraphQL BFF operations for caregivers
care-pp-cli caregivers booking-list-provider - Fetch caregivers booking list providercare-pp-cli caregivers get - Fetch caregiverscare-pp-cli caregivers profile - Fetch caregivers profile
conversations
GraphQL BFF operations for conversations
care-pp-cli conversations - Fetch conversations most relevant care needs
members
GraphQL BFF operations for members
care-pp-cli members entitlements - Fetch members entitlementscare-pp-cli members ids - Fetch members ids
memberships
GraphQL BFF operations for memberships
care-pp-cli memberships - Fetch memberships information
messages
GraphQL BFF operations for messages
care-pp-cli messages - Fetch messages thread
notifications
GraphQL BFF operations for notifications
care-pp-cli notifications counts - Fetch notifications countscare-pp-cli notifications counts-2 - Fetch notifications counts
providers
GraphQL BFF operations for providers
care-pp-cli providers child-care - Fetch providers child carecare-pp-cli providers child-care-2 - Fetch providers child carecare-pp-cli providers get - Fetch providers
reviewees
GraphQL BFF operations for reviewees
care-pp-cli reviewees - Fetch reviewees metrics
reviews
GraphQL BFF operations for reviews
care-pp-cli reviews by-reviewee - Fetch reviews by revieweecare-pp-cli reviews request-search - Fetch reviews request search
seekers
GraphQL BFF operations for seekers
care-pp-cli seekers get - Fetch seekerscare-pp-cli seekers job-application - Fetch seekers job applicationcare-pp-cli seekers job-summaries - Fetch seekers job summariescare-pp-cli seekers membership-information - Fetch seekers membership information
zipcodes
GraphQL BFF operations for zipcodes
care-pp-cli zipcodes - Fetch zipcodes summary
Self-learning loop
This CLI caches per-question discovery so repeat queries skip the walk and structurally similar queries get answered via entity substitution. The loop also self-captures: every invocation is journaled locally, and failed-flag corrections plus fresh teaches surface as candidates on the next recall for confirm/reject judgment. Agents call recall before discovery and fire teach & after answering. See the ## Automatic learning section in SKILL.md for the full protocol.
care-pp-cli recall <query> - Look up cached resources for a query before running discoverycare-pp-cli teach - Record a query -> resource mapping (silent on success, safe to background with &)care-pp-cli learnings list - Inspect taught rowscare-pp-cli learnings forget <query> - Undo a teachcare-pp-cli learnings candidates - List auto-captured candidates awaiting confirm/rejectcare-pp-cli learnings stats - Local loop metrics: recall hit rate, teach-to-reuse, playbook resolution, candidate countscare-pp-cli teach-pattern - Install a query/resource template up frontcare-pp-cli teach-lookup - Add an entity mapping (e.g. country code, team alias) for pattern substitution
Pass --no-learn or set CARE_NO_LEARN=true to disable the loop for deterministic flows.
The local store's schema version stamp is one-way: once this version of care-pp-cli opens the database, older binaries refuse it with a version error — upgrade the binary rather than downgrading.
Output Formats
# Human-readable table (default in terminal, JSON when piped)
care-pp-cli calendars --operation-name GetCalendar
# JSON for scripting and agents
care-pp-cli calendars --operation-name GetCalendar --json
# Filter to specific fields by name
care-pp-cli calendars --operation-name GetCalendar --json --select <field>[,<field>...]
# Dry run — show the request without sending
care-pp-cli calendars --operation-name GetCalendar --dry-run
# Agent mode — JSON + compact + no prompts in one flag
care-pp-cli calendars --operation-name GetCalendar --agent
--csv prefixes a leading ' on cells and header keys that start with =, +, -, @, a tab, or a line break (including fullwidth ＝＋－＠) so a spreadsheet does not run them as formulas. Plain signed numbers such as -5 and +2.5e3 are left unchanged.
Agent Usage
This CLI is designed for AI agent consumption:
- Non-interactive - never prompts, every input is a flag
- Pipeable -
--json output to stdout, errors to stderr
- Filterable -
--select <field>[,<field>...] returns only fields you need
- Previewable -
--dry-run shows the request without sending
- Explicit retries - add
--idempotent to create retries when a no-op success is acceptable
- Explicit confirmation -
--agent does not imply --yes; pass --yes separately only after the target, arguments, and side effects are clear
- Piped input - write commands can accept structured input when their help lists
--stdin
- Agent-safe by default - no colors or formatting unless
--human-friendly is set
Exit codes: 0 success, 2 usage error, 3 not found, 4 auth error, 5 API error, 6 partial failure, 7 rate limited, 10 config error.
Health Check
care-pp-cli doctor
Verifies configuration, credentials, and connectivity to the API.
Configuration
Run care-pp-cli doctor to see the resolved config, data, state, and cache directories. The platform-default config path is ~/.config/care-pp-cli/config.toml on macOS/Linux and %USERPROFILE%\.config\care-pp-cli\config.toml on Windows; --home, CARE_HOME, and per-kind env vars can relocate it.
Static request headers can be configured under headers; per-command header overrides take precedence.
--ca-cert, CARE_CA_CERT, or ca_cert adds a PEM CA bundle to the system trust roots. --tls-server-name, CARE_TLS_SERVER_NAME, or tls_server_name is the name checked against the certificate when the dialed address does not match it. Precedence is flag, then environment, then the config file. A config file other users can change does not supply these settings. Certificate verification failures are not retried.
Troubleshooting
Authentication errors (exit code 4)
- Run
care-pp-cli doctor to check credentials
Not found errors (exit code 3)
- Check the resource ID is correct
- Run the
list command to see available items
HTTP Transport
This CLI uses Chrome-compatible HTTP transport for browser-facing endpoints. It does not require a resident browser process for normal API calls.
TLS certificates are verified by default. For a trusted development or self-signed endpoint only, pass --insecure for one invocation, set CARE_SKIP_TLS_VERIFY=true for the current environment, or set skip_tls_verify = true in the config file for a persistent override. --insecure overrides --ca-cert and --tls-server-name.
Generated by CLI Printing Press