Kasvu
Review training data and propose plans you choose to accept.
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
Kasvu connects an athlete’s training account to Claude so it can review recovery, strength sessions, walks, runs, rides, personal bests, training load, and the active program. It can explain the current coaching-plan format, preview a training week, save coaching notes and intake answers, and propose validated programs, daily changes, progress measures, or watchlists. Proposals remain pending until the athlete accepts them in the Kasvu iPhone app; the connector cannot activate a plan or log completed workouts. Training prescriptions and progression safeguards come from Kasvu’s deterministic planning engine. A Kasvu account with Pro connector access is required; Claude plan requirements apply separately. Kasvu provides training information, not medical diagnosis or treatment.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-09-14
- Tool count
- 17
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Discoverability Score
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
17 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.