What Sprout is
Sprout is the operating system for the family, driven by your home agent and the Sprout agent.
How it works
Your agent is the bridge to your home systems. The Sprout agent works the inside.
You connect your agent once over OAuth. From then on it reads and writes family state through the Sprout MCP: pull the roster, ship a task to your kid, save a skill, schedule a recurring check-in. The kid does the thing, earns gems, spends them on rewards or screen-time. Sprout runs the surface and the economy. You run everything else.
Sprout is an MCP-guided service, not an API you wire by hand. Your agent reads the live tool catalog and the authoring guide at runtime, so these pages are the map, not the spec. They tell you what the pieces are, where the seams sit, and what bites. The exact call signatures live in the MCP.
The cast
Two agents drive. The Sprout apps surface it. Sprout Systems orchestrates.
- Your agent. Owns intent. Lives in your home systems. Talks to Sprout Systems over MCP.
- The Sprout agent. Powers the in-app agentic moments, especially for your kids. An accessible assistant within the Sprout apps for parents.
- Parent app. Onboarding and setup; a surface to quickly view, respond to, and add things to Sprout Systems, with help from the Sprout agent.
- Kid app. Where your kids experience Sprout. (More apps to come: villager, coach…)
- Sprout Systems. The platform and the data underneath it all. Family state, the gem economy, the skill lifecycle, the screen-time gates. Routes between the agents and the apps.
The full breakdown, including where the lines are drawn and the failure modes you will hit, is in The cast.
Start here
Three more pages, in order. By the end you have a skill in your library and a working task on a kid's iPad.
- Plug your agent in. One OAuth handshake. Common pitfall: the default scope set may miss
canvas:*orskill:*; reconnect to pick up the full set. - Your first task. Read the family, create the task. Two MCP calls; no skill, no canvas. Lands on the kid's iPad.
- Save it as a skill. Wrap that task into a
home_agentskill so your agent can fire it again tomorrow with one call.
Further reading
The nouns Skill lifecycle The cast