find_linkedin_profile — PeopleSearch.im MCP Tool Read-only
find_linkedin_profile
(find linkedin profile) is one of 12 tools on the
PeopleSearch.im
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call find_linkedin_profile from your client
- Claude Code PeopleSearch.im find_linkedin_profile run in your project directory
- Claude Desktop PeopleSearch.im find_linkedin_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PeopleSearch.im find_linkedin_profile ~/.cursor/mcp.json
- VS Code PeopleSearch.im find_linkedin_profile .vscode/mcp.json
- Zed PeopleSearch.im find_linkedin_profile ~/.config/zed/settings.json
- Windsurf PeopleSearch.im find_linkedin_profile ~/.codeium/windsurf/mcp_config.json
- Cline PeopleSearch.im find_linkedin_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PeopleSearch.im find_linkedin_profile ~/.gemini/settings.json
- Grok PeopleSearch.im find_linkedin_profile .mcp.json (in your project root)
- ChatGPT PeopleSearch.im find_linkedin_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai PeopleSearch.im find_linkedin_profile Settings → Connectors → Add custom connector
- LangChain PeopleSearch.im find_linkedin_profile pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http email-finder https://peoplesearch.im/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.