Community systems · Shipped
CP Mentorship, and giving the assistant real tools
The platform under cpmentorship.org: the public site, the member portal, committees, directory and event check-in, plus MCP tools that let Claude Code operate the admin directly.
TypeScript, Google Cloud, MCP ·
What it found
Giving an assistant real tools replaced a backlog of admin screens. Every operation exposed as a tool was one screen that never needed designing, and the two-step confirmation is what made it safe enough to mean it.
The work
What was actually built
A mentorship organisation runs on administration: cohorts, pairings, committees, events, check-ins, a people directory. All of it ordinarily becomes admin screens, and admin screens become a backlog nobody finishes.
The platform is live at cpmentorship.org, hosted on Google Cloud. The experiment was the last part: instead of building the next twenty admin screens, expose the operations as MCP tools so an assistant can do the work directly. Create a draft event. Pair a mentor and a mentee. Look up a contact. Publish a page, behind a two-step confirmation so nothing goes live by accident.
That is a different shape of product. The console stops being the only way in.
Still open
What this did not settle.
What happens when the tools outnumber the staff who understand them?
The safety model is a typed confirmation on anything destructive or public. That holds while the operator knows what they are confirming. It is untested with somebody new.
See it
Open it, or read the code.
cpmentorship.org. Opens in a new tab on an external site.