how_to_get_leads — TutorPing MCP Tool
how_to_get_leads
(how to get leads) is one of 8 tools on the
TutorPing
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call how_to_get_leads from your client
- Claude Code TutorPing how_to_get_leads run in your project directory
- Claude Desktop TutorPing how_to_get_leads ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TutorPing how_to_get_leads ~/.cursor/mcp.json
- VS Code TutorPing how_to_get_leads .vscode/mcp.json
- Zed TutorPing how_to_get_leads ~/.config/zed/settings.json
- Windsurf TutorPing how_to_get_leads ~/.codeium/windsurf/mcp_config.json
- Cline TutorPing how_to_get_leads ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TutorPing how_to_get_leads ~/.gemini/settings.json
- Grok TutorPing how_to_get_leads .mcp.json (in your project root)
- ChatGPT TutorPing how_to_get_leads Settings → Connectors → Advanced → Developer mode
- Claude.ai TutorPing how_to_get_leads Settings → Connectors → Add custom connector
- LangChain TutorPing how_to_get_leads pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tutorping https://tutorping.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 2 October 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.