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