The MCP Server, explained.
MCP (Model Context Protocol) is the open standard that lets AI coding tools — Lovable, Cursor, Claude, Windsurf — ask outside services for the context they need. Hold My Hand ships a tiny MCP server so your AI already knows what your product is, who it's for, and what users typically try to do.
A spec endpoint
One URL returns a clear instruction set: scan the app, write a context file, install the widget.
A product context file
Your AI fills in app overview, audience, glossary, and common tasks — all stored alongside the API key.
Grounded answers
Runtime answers reuse the context file, so users get accurate guidance instead of hallucinated paths.
One paste in your AI tool sets everything up.
- 1Drop our setup prompt into Lovable, Cursor, Windsurf, or Claude Code.
- 2Your AI calls the MCP endpoint and reads the instructions.
- 3It explores your app, fills out a context file at public/holdmyhand.map.json, and installs the SDK in <head>.
- 4When users click the help button, answers are grounded in that file plus a live DOM scan.
Real pains, solved on day one.
SaaS onboarding without writing docs
Your AI ingests every screen via MCP and answers "how do I invite a teammate?" with a spotlighted control — no docs maintained.
Internal tools nobody understands
Drop the MCP setup into a private dashboard. New engineers stop pinging Slack — they ask the widget and get the right tab highlighted.
Course / tutorial platforms
Tell users exactly which lesson, button, or setting to open next without forcing them to search through menus.
Compliance & admin consoles
Walk auditors through verification flows step-by-step, with the path explained when controls are buried in submenus.