how_to_get_a_pro — LocalHelpNow MCP Tool
how_to_get_a_pro
(how to get a pro) is one of 3 tools on the
LocalHelpNow
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call how_to_get_a_pro from your client
- Claude Code LocalHelpNow how_to_get_a_pro run in your project directory
- Claude Desktop LocalHelpNow how_to_get_a_pro ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LocalHelpNow how_to_get_a_pro ~/.cursor/mcp.json
- VS Code LocalHelpNow how_to_get_a_pro .vscode/mcp.json
- Zed LocalHelpNow how_to_get_a_pro ~/.config/zed/settings.json
- Windsurf LocalHelpNow how_to_get_a_pro ~/.codeium/windsurf/mcp_config.json
- Cline LocalHelpNow how_to_get_a_pro ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LocalHelpNow how_to_get_a_pro ~/.gemini/settings.json
- Grok LocalHelpNow how_to_get_a_pro .mcp.json (in your project root)
- ChatGPT LocalHelpNow how_to_get_a_pro Settings → Connectors → Advanced → Developer mode
- Claude.ai LocalHelpNow how_to_get_a_pro Settings → Connectors → Add custom connector
- LangChain LocalHelpNow how_to_get_a_pro pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http localhelpnow https://localhelpnow.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.