kiddinglab for AI assistants
kiddinglab runs a public Model Context Protocol (MCP) server and a plain HTTP API so AI assistants like Muse, Claude and ChatGPT can help parents find kids' camps in the DC, Maryland, and Virginia area. Both expose the same public camp data you can browse on this site — no account or API key required, and no browser automation needed.
Organizers: to push your own camp's sessions to kiddinglab, see the Organizer Listing API.
Endpoints
- MCP server (Streamable HTTP):
https://www.kiddinglab.com/mcp - HTTP API:
https://www.kiddinglab.com/api/v1/— OpenAPI 3.1 spec at https://www.kiddinglab.com/openapi.json
Quick start by assistant
Meta Muse
Muse has no settings screen for MCP servers: you set one up by sending Muse a single chat message, and it builds, tests and saves the connector as a skill. Paste this:
Build a Custom Connector to the MCP server at https://www.kiddinglab.com/mcp (HTTP, no authentication). List its tools, test search_camps with ZIP 20852, and save it as a skill named kiddinglab. If Muse asks for an authentication method, answer "none". You can also hand it the OpenAPI document (https://www.kiddinglab.com/openapi.json) instead of the MCP URL.
Claude
On claude.ai: Settings → Connectors → Add custom connector, URL https://www.kiddinglab.com/mcp. In Claude Code:
claude mcp add --transport http kiddinglab https://www.kiddinglab.com/mcpChatGPT
Settings → Connectors → enable developer mode → add a remote MCP server with URL https://www.kiddinglab.com/mcp, no authentication. For a Custom GPT, import the action from https://www.kiddinglab.com/openapi.json.
Any HTTP client
curl "https://www.kiddinglab.com/api/v1/camps/search?zip=20852&ages=7"Available tools
Each tool is one MCP tool and one HTTP endpoint; the operationId in the OpenAPI spec equals the MCP tool name, and HTTP query parameters are named exactly like the tool's arguments (array values are comma-separated).
- search_camps — Search sessions by ZIP (or lat+lon, or city+state), dates, ages, categories and price. Listed prices per session, plus parent_price_usd (fee-inclusive) for sessions bookable on kiddinglab.
GET https://www.kiddinglab.com/api/v1/camps/search?zip=20852&ages=7,9&start_date=2027-06-15&end_date=2027-08-15 - find_camp_by_name — Look a camp up by (approximate) camp or organization name.
GET https://www.kiddinglab.com/api/v1/camps/lookup?name=Steve%20and%20Kate - get_camp_details — One camp: description, organizer, rating, and all sessions with the camp's listed prices (and parent_price_usd where bookable on kiddinglab).
GET https://www.kiddinglab.com/api/v1/camps/{camp_id} - get_sessions_and_availability — Live bookability, price, deposit and remaining spots for up to 20 sessions — price_usd is the camp's price, parent_price_usd what the parent pays before tax — plus booking_mode and, for camps on a connected registration platform, the platform-reported status, its freshness and the registration link.
GET https://www.kiddinglab.com/api/v1/sessions/availability?sess_ids=101,102,103 - get_booking_policies — Refund policy, payment schedule, waiver requirement and payment facts for one session, including the fee-inclusive parent_price_usd and parent_deposit_usd.
GET https://www.kiddinglab.com/api/v1/sessions/{sess_id}/policies - create_booking_handoff — A prefilled checkout link for the parent (valid 24 hours) for sessions with booking_mode native, with total_usd (camp prices) and parent_total_usd (what the parent pays before tax). Holds no spots, carries no child names, books nothing. Sessions registered on the camp's own platform, stale platform reports and full sessions are refused with their registration_url.
POST https://www.kiddinglab.com/api/v1/booking-handoffs Content-Type: application/json {"items":[{"sess_id":101,"children_count":1}]}
HTTP API conventions
- Responses are the same JSON object the MCP tool returns. Prices are in US dollars (see Prices and the service fee).
- Errors are
{"error":{"code","message","issues?"}}with400 invalid_input,404 not_found,429 rate_limited(withRetry-After) or503 unavailable. - Identify your client with an optional
X-Agent-Client: name/versionheader. - CORS is open, so browser-based agents and playgrounds can call the API directly.
How booking works
Assistants search and prepare; parents decide. An assistant can find camps, compare sessions, check availability, and hand the parent a prefilled checkout link via create_booking_handoff. Every booking is then completed by the parent on kiddinglab.com — they sign in, review the details, name their campers, sign waivers, and pay. Assistants are never able to place a booking or charge a payment method on a parent's behalf, and no capacity is reserved until the parent checks out.
Prices and the service fee
Since version 1.4.0 every price field says whose price it is. price_usd, price_usd_min / price_usd_max, deposit_usd and total_usd are the camp's own prices. For sessions booked on kiddinglab.com (booking_mode native) the response also carries:
parent_price_usd— what the parent pays for the session before tax: the camp's price plus Kiddinglab's 1.5% service fee. Quote this number to parents, never the bareprice_usd.service_fee_usd— the service fee itself (1.5% of the camp's price, rounded to the cent).parent_deposit_usd— the deposit due at checkout including its share of the fee, where the camp takes a deposit.parent_total_usdandservice_fee_total_usdon a create_booking_handoff response — the same figures summed over the handoff's items and children.
The fee is itemized again at checkout, applies to every payment method, and is the only fee a parent pays: card processing is never charged to parents, and paying by bank transfer may earn a small discount shown at checkout. Tax, where a camp collects it (tax_rate), is added at checkout. Sessions with any other booking_mode are registered off kiddinglab.com, so their prices are the camp's listed prices and carry no fee fields. See the Terms of Service ("Fee Structure").
Registration platforms and booking_mode
Since version 1.3.0 every session carries a booking_mode:
- native — booked on kiddinglab.com; use create_booking_handoff.
- platform_deeplink — the camp's own registration platform (for example Jackrabbit, WooCommerce or LeagueApps) is connected to kiddinglab. Send the parent to
registration_url. Theavailabilityobject is what that platform reported (status,kind,fetched_at,stale): remaining spots are exact below 10 and "10+" above, hidden once the report is older than 24 hours, and availability is confirmed only when the parent registers on the platform.blocked_reasonisexternal_registration, oravailability_stalewhen the last report is more than 7 days old. - listing_only — register on the camp's own website (
registration_url).
Treat any blocked_reason you do not recognise as "not bookable on kiddinglab; use registration_url" — the set may grow. A refused create_booking_handoff answers 400 invalid_input with each refused session's registration_url in the message.
Privacy
Both interfaces serve only public camp listings. They never return personal information about parents, children, or bookings, and require none to use. See our Privacy Policy and Terms of Service.
Rate limits
60 requests per minute per IP address, counted separately for the MCP server and the HTTP API. Requests above the limit return HTTP 429 with a Retry-After header.
Discovery
- MCP registry name:
com.kiddinglab/kiddinglab; manifest at https://www.kiddinglab.com/.well-known/mcp.json. - Machine-readable site summary: https://www.kiddinglab.com/llms.txt.
- Every page links the API description from its
<head>(rel="service-desc") and this guide (rel="service-doc").
Contact
Questions or issues integrating with the MCP server or HTTP API? Email support@kiddinglab.com.