Plug your agent in - Sprout for Builders

warningFinish Sprout onboarding first. Authentication binds to a parent account with a set-up family, so the parent must have completed onboarding in the Sprout app (a family with at least one kid) before you connect. Connect before that and there is no family for your agent to act on.

What you point at

Endpoint	`https://api.sproutgoodhabits.com/mcp`
Transport	HTTP (streamable)
Auth	OAuth. Approve in your client after adding.

Add it to your client

Sprout works with any MCP client. A few common ones are below. For anything else, follow that client's own MCP integration guide and point it at the endpoint above.

Shell

claude mcp add --transport http sprout https://api.sproutgoodhabits.com/mcp

Then run /mcp, select sprout, and complete the OAuth prompt in your browser.

Shell

codex mcp add sprout --url https://api.sproutgoodhabits.com/mcp
codex mcp login sprout

The first command registers the server (stored in ~/.codex/config.toml under [mcp_servers.sprout]; you can also add it by hand). The second opens the OAuth prompt in your browser. Once you authorize, start Codex and run /mcp to confirm the Sprout tools are listed.

infoIf your Codex build does not complete the OAuth prompt for a URL server, bridge it with mcp-remote: set command = "npx", args = ["-y", "mcp-remote", "https://api.sproutgoodhabits.com/mcp"].

Add Sprout under mcpServers in ~/.openclaw/openclaw.json, then restart the gateway:

JSON

{
"mcpServers": {
"sprout": {
"url": "https://api.sproutgoodhabits.com/mcp"
}
}
}

Or use the built-in mcporter skill to add and authenticate it from chat. Complete the OAuth prompt when it appears.

In ChatGPT, go to Settings > Apps > Advanced Settings > Developer Mode and turn it on. Then Create App, add Sprout's details (name sprout, the endpoint above), and complete the OAuth flow.

infoDeveloper Mode is what exposes custom MCP apps and their write tools; it requires a paid ChatGPT plan.

Scopes

Sprout uses OAuth 2.0. Each scope maps to a family of MCP tools. Connection is all-or-nothing today: the parent sees the full list and approves it as one set at consent time. Approve everything you might want to use; adding a scope later requires a full reconnect, which interrupts the parent.

Scope	Tier	Tools unlocked
`family:read`	Read	`family.query_overview`
`task:read`	Read	`task.list`, `task.review`
`task:write`	Write	`task.create`, `task.update`, `task.complete`, `task.delete`
`skill:read`	Read	`skill.list`, `skill.get`
`skill:write`	Write	`skill.write`, `skill.update`, `skill.invoke`, `skill.post_result`
`canvas:read`	Read	`canvas.list`, `canvas.get`
`canvas:write`	Write	`canvas.create`, `canvas.update`
`reward:read`	Read	`reward.list`
`reward:write`	Write	`reward.create`, `reward.update`
`heartbeat:read`	Read	`heartbeat.list`, `heartbeat.describe`
`heartbeat:write`	Write	`heartbeat.create`, `heartbeat.update`
`screentime:read`	Read	`screentime.list_requests`, `screentime.query_state`
`gems:read`	Read	`gems.query_balance`, `gems.list_transactions`
`project:read`	Read	`project.list`, `project.get`
`gems:adjust`	High	`gems.adjust`
`screentime:approve`	High	`screentime.review_request`

Verify it worked

Shell

mcp.whoami
# Look at the sprout_scopes array. If you're missing canvas:write or skill:write,
# disconnect and reconnect to pick up the full set.

tips_and_updatesNow you can: your agent reads and writes family state through Sprout. Next, ship something a kid can see.

Was this page helpful?