Cursor
Cursor · MCP settings
Add the Engine MCP server in Cursor Settings → Tools & MCP (or `.cursor/mcp.json`). Reviews and CTO context stay in the agent loop while you vibe-code in the IDE.
Cursor MCP settings ↗Service
Fractional CTO as a service
You build — with the safety of someone on your shoulder, ready to talk as you work with your AI. Code review lands in Cursor MCP settings and the same Claude and OpenAI connectors you already use to vibe-code.
You build with AI
Ship in your vibe-coding loop — Cursor, Claude, ChatGPT. I do not take the keyboard; I keep the architecture and judgment honest.
Code review in the tools
Reviews run through connectors that sit next to your model. Catch drift early without a separate ticket queue.
Shoulder when it matters
Paid packages add a private calendar and weekly progress reviews — someone ready to talk while you work.
Connectors
Engagement runs through hosted Engine tools in Cursor, Claude, and ChatGPT — one policy boundary, same reviews and context wherever you build.
Claude
Anthropic · Claude
Connect Claude to the same Engine tools I use for reviews, context, and follow-ups — so feedback lands inside the chat where you are already building.
Claude custom connectors ↗
ChatGPT
OpenAI · ChatGPT
Same connector boundary in ChatGPT — ask for a review, pull status, or prep a weekly progress pass without leaving your OpenAI workspace.
ChatGPT connectors ↗What is included
Free · all subscribers
Free
- Code review via vibe-coding tools
Larger packages
Private calendar · weekly progress reviews
- Code review via vibe-coding tools
- Private calendar for live check-ins
- Weekly progress reviews
- Someone on your shoulder while you build with AI