sync_linkedin_connections — LinkedIn MCP Server (Salesbot) MCP Tool Mutating
sync_linkedin_connections
(sync linkedin connections) is one of 72 tools on the
LinkedIn MCP Server (Salesbot)
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call sync_linkedin_connections from your client
- Claude Code LinkedIn MCP Server (Salesbot) sync_linkedin_connections run in your project directory
- Claude Desktop LinkedIn MCP Server (Salesbot) sync_linkedin_connections ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LinkedIn MCP Server (Salesbot) sync_linkedin_connections ~/.cursor/mcp.json
- VS Code LinkedIn MCP Server (Salesbot) sync_linkedin_connections .vscode/mcp.json
- Zed LinkedIn MCP Server (Salesbot) sync_linkedin_connections ~/.config/zed/settings.json
- Windsurf LinkedIn MCP Server (Salesbot) sync_linkedin_connections ~/.codeium/windsurf/mcp_config.json
- Cline LinkedIn MCP Server (Salesbot) sync_linkedin_connections ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LinkedIn MCP Server (Salesbot) sync_linkedin_connections ~/.gemini/settings.json
- Grok LinkedIn MCP Server (Salesbot) sync_linkedin_connections .mcp.json (in your project root)
- ChatGPT LinkedIn MCP Server (Salesbot) sync_linkedin_connections Settings → Connectors → Advanced → Developer mode
- Claude.ai LinkedIn MCP Server (Salesbot) sync_linkedin_connections Settings → Connectors → Add custom connector
- LangChain LinkedIn MCP Server (Salesbot) sync_linkedin_connections pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http linkedin-mcp-server https://app.salesbot.cz/api/mcpOther tools on this server
- search_linkedin_people
- search_google_xray
- upsert_linkedin_contact
- add_contacts_to_list
- remove_contacts_from_list
- enrich_contacts
- search_linkedin_navigator
- import_linkedin_company_list
- list_company_lists
- list_companies
- update_company_research
- add_companies_to_crm
- list_crm_companies
- get_crm_company
- update_crm_company
- merge_crm_companies
- add_contacts_to_crm
- get_contact_profile
- list_contacts
- search_crm_leads
- list_lead_lists
- create_lead_list
- list_blacklist
- check_blacklist
- list_campaigns
- list_campaign_queue
- list_mcp_pending_actions
- add_contacts_to_campaign
- exclude_contacts_from_campaign
- send_linkedin_message
- send_connection_request
- get_daily_limits
- generate_campaign_message
- prepare_campaign_messages
- list_pending_approvals
- approve_message
- reject_message
- publish_linkedin_post
- list_inbox_chats
- get_chat_messages
- reply_to_chat
- mark_chat_read
- create_campaign
- update_campaign_settings
- start_campaign
- stop_campaign
- scrape_website
- get_linkedin_status
- connect_linkedin
- set_deal_stage
- log_crm_note
- create_task
- save_lead_message
- list_lead_messages
- get_lead_context
- export_crm
- update_contact
- update_crm_lead
- list_tasks
- complete_task
- list_crm_stages
- add_crm_stage
- rename_crm_stage
- delete_crm_stage
- list_crm_fields
- add_crm_field
- delete_crm_field
- set_lead_fields
- search_job_postings
- search_web
- get_job_posting_details
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.