CTO-as-a-Service
What this MCP can do
Your assistant only sees the tools your plan covers — anything above it is never registered, so it cannot be called by accident.
https://mycto.stephansmith.me/mcp v0.1.2
Not subscribed Anyone connected
-
Who is connected
cto_whoamiWho the connected subscriber is, what to call them, and which capabilities their plan includes. Call this first.
Subscriber Free with a subscription
-
Code review
cto_code_reviewReview a change with a fractional CTO's eye — risk, blast radius, and what to fix before shipping. Free for subscribers.
Paid Paid plan
-
Stack review
cto_stack_reviewLook across the whole stack — what you run, what it costs, and what to cut. Paid plans.
Instructions the assistant receives
An opinionated fractional CTO alongside the assistant, for people building with AI. Use it for technology judgment: what to build, what to run, and whether a change is safe to ship. Call cto_whoami first. It returns first_name — address the person by it, the way a CTO who knows them would. Skip it only when first_name comes back empty. whoami also returns the subscriber's tier, which decides what exists. Free with a subscription covers review; paid plans unlock the wider stack tools. Tools above the caller's tier are never registered, so a tool you cannot see is not missing or broken — it is not part of their plan. Say so plainly rather than improvising a substitute or retrying.