Assign play
Choose released games and settings. Send a versioned plan for the family to review.
ROOM TO PLAY. SUPPORT TO GROW.
Bring Cubby into
your care platform.
Connect your EMR, clinic tools, or AI assistant to family-approved play plans and shared progress.
Independent of Trellis. The same API for every integration.
Partner sandbox is online.Provisioned keys required. Fictional data only. Real clinic access and live billing remain closed.Service health ↗
Receive progress
Read deliberately shared snapshots with source IDs, digests, and separate review notes.
Keep control
Use clinic-scoped keys, revocable connections, safe retries, and paged event polling.
QUICK START
A clear path from
sandbox to integration.
Request a workspace from the Cubby owner with your integration name, technical contact, desired scopes, and data flow.
You receive private configuration files, separate read and write keys, and fictional fixture IDs. Partner onboarding is managed by the owner.
Partner acceptance checklist ↗Get your workspace
Start with a read-only key. Keep it on your server and outside source control.
Run the examples
Unpack the kit. Set the private configuration path. Use Node.js 24 or newer.
PowerShell
$env:CUBBY_CONFIG_FILE = 'C:/private/cubby.json'
node examples/quickstart.mjs
node examples/contract-test.mjsVerify your data flow
Test chart binding, isolation, consent revocation, retries, and clinician review before a real clinic pilot.
PARTNER REST API
One contract. Your tools.
HTTPS JSON with bearer credentials. The reference below is rendered from the published specification. Expand an endpoint to inspect its permissions, request schema, and response schema.
Sandbox API base URL
https://developers.cubby.3-21-209-244.sslip.io/api/v1Loading API reference…
No outgoing push webhooks, SMART, FHIR, or OAuth service in this preview. Events use a paged polling feed. New plan revisions need family acceptance.
MCP FOR AI CLIENTS
The same controls.
A tool interface.
Run the included MCP server locally. It connects to the HTTPS API with your clinic key. Start with read tools, then enable approved writes only when your host and workflow are ready.
Download client configuration template ↗Install the MCP package
npm ci --prefix mcp
# Configure your client to launch:
node /absolute/path/to/mcp/server.mjs
# Environment: CUBBY_CONFIG_FILE=/private/cubby.jsonRead tools
Catalog · Connections · Assignments · Report list · Plan · Report · Events
Optional write tools
Assign a plan · Save a review note
Stdio transport with modern discovery and legacy client support. No remote MCP URL. Writes require scope, explicit configuration, and approval from the host user.
FAMILIES STAY IN CONTROL
A connection is permission,
not a shortcut.
API keys and AI tools cannot approve consent, create child accounts, share a report for a parent, or charge a family. Treat shared notes as untrusted data. Map opaque IDs to a verified chart and keep clinician review in your workflow.