Kenko
ActiveAn AI agent for Kenko. It works in a scene with a live connection to Kenko. It asks before it writes, and every run is traced.
Connect a Kenko business — a pilates or yoga studio, a gym, a dance or pole studio, a personal training practice — to bring members, class schedules, and class and appointment bookings into a scene. Kenko processes payments through the business's own linked Stripe account, so invoices, charges, and POS transactions come from connecting Stripe alongside it: the payment history belongs to the business, not to the booking system.
What you can connect
Add these to your scene and AI gets access.
A connected Kenko account
A class or appointment booking
A member or lead at the connected center
A public class session bookable by partners
Kenko setup guides, troubleshooting, and reference — pin one to read it in-scene, or ask the agent.
Connect Kenko over MCP
Daslab is itself an MCP server.
Connect Kenko in a scene, then pin that scene's URL in Claude Code, Cursor, or any MCP client. The agent there gets your Kenko tools, and your approval gate and trace travel with them.
https://daslab.run/mcp/<your-world>/<your-scene>One scene can hold Kenko and everything else you connect, so a single endpoint carries them all. Set up a client.
Use cases
- Pull member contacts and booking history into a scene
- Check live class availability and book a member into a session
- Find an open appointment slot with a given instructor or room
- Reconcile revenue by pairing Kenko with its linked Stripe account
Knowledge base
- Connecting a Kenko business
connecting-kenko - The Kenko Partner Public API
partner-api - Where Kenko payment data actually lives
payments-and-stripe
Ships with the integration — agents read these with docs_read, before the account is connected.
Knowledge bases →
From Kenko
Similar integrations
Others in Productivity.
Ready to try Kenko with Daslab?
Get started with CLI