Permissions
What an app connected by signing in can read and do.
How permissions work
When you connect an app, the consent screen lists the permissions it asks for. Each tool needs one permission. A tool whose permission was not granted is refused, and the app can ask you for that permission and connect again.
Betterness (https://api.betterness.ai/mcp)
| Permission | What it allows |
|---|---|
health:read | Read health data: activity, sleep, vitals, biomarkers, nutrition, Program |
log:write | Log meals, supplements, water, measurements and workouts |
documents:read | List and read documents |
documents:write | Add documents |
profile:write | Update profile, contact, health profile and devices |
inbox:read | Read Inbox conversations |
inbox:write | Send Inbox messages, after you confirm |
program:write | Propose a Program |
labs:order | Order, book, reschedule and cancel lab tests, after you confirm |
purchases | Buy lab tests, after you confirm |
Betterness One (https://api.betterness.one/mcp)
See Betterness One permissions.
Actions that wait for you
Buying a lab test, booking, rescheduling or cancelling an appointment, sending an Inbox message and publishing a post happen in two steps. The first tool shows you exactly what will happen and returns a confirmation. Nothing is charged, booked, sent or published until you approve it in the chat and the app confirms it.
API keys
A bk_* API key can be narrowed to the same permissions when you create it. A key with no permissions selected holds all of them.