LinkedIn MCP Server (Salesbot)

Search people on LinkedIn by keywords, title, location or company. Results are saved directly into your contacts (with deduplication and blacklist filtering) and the tool returns IDs that the AI uses in other tools. Pass either `location` (human name like 'Praha', 'Berlin', 'Czechia') or `locationId

Google X-Ray search for public LinkedIn profiles via Google operators (site:linkedin.com/in). Useful when you don't want to consume LinkedIn search limits. Found profiles are saved into your contacts (in a 'Google X-Ray' list, deduplicated by profile URL) and the tool returns their contact_id values

Enrich existing contacts with their full LinkedIn profile data via the connected LinkedIn account (Unipile) — headline, location, current company & position, full experience, education and skills are scraped from each contact's profile URL and saved onto the contact (and merged into profile_data). U

Scrape a Sales Navigator (or standard LinkedIn) search URL. Pass a ready-made search URL with filters already set; leads are saved into contacts and their IDs are returned.

Return the full contact profile from the database — name (with Czech vocative), headline, company, role, location, language, current campaign status and interaction history. Used as context for personalized messages or next-step decisions.

List contacts in a specific lead list with ID, name, headline, company, profile URL, gender and current status (e.g. invite_sent, connected, replied). The AI picks IDs from this list for further tools.

List your campaigns with ID, name, status (draft/running/paused), description and lead counts. Use this to obtain campaign_id when adding leads, generating messages or approving drafts.

Add selected contacts (by ID) to an existing campaign. Blacklist of domains/companies, duplicate checks and manual exclusion are applied automatically. Campaign steps (visit → connect → message) are then scheduled per template and daily limits. Returns how many were added vs filtered.

Send a one-off LinkedIn message to a specific contact outside any campaign. A random 30–180 s delay is applied before sending for anti-detection. The action counts against the daily message limit, respects allowed hours, and is logged in interactions.

Send a LinkedIn connection invitation. The message is ALWAYS empty (no text) — policy choice to avoid account blocks, regardless of account type (free or premium). Enforces daily invitations limit, allowed hours, blacklist, random delays and usage tracking.

Check remaining daily quota for a profile. Returns current usage vs limits, ramp-up status, allowed hours, and whether actions are currently allowed. profile_id is optional — if omitted, the user's active (or first) profile is used; if no profile exists, the error response lists all available profil

Generate (or regenerate) an AI personalized message draft for a specific campaign_contact and step, using the template and lead profile. The message is NOT sent — it is stored as a draft with status 'pending_approval' and waits for review (via this MCP or manually). Use list_pending_approvals + appr

Return all AI drafts waiting for approval (messages_approved=false). Each draft includes the contact name, headline, company and generated text. Used as input for bulk review by an AI assistant which can iterate through drafts and approve/reject them. Optionally filter by campaign_id.

Approve a draft and hand it to the campaign executor for sending (respecting daily limits and allowed hours). Optionally pass edited_messages to overwrite specific drafts before approval. By default each draft is verified by a second-pass quality check (Czech vocative, hallucinations, prompt adheren

Reject the current drafts on a campaign_contact with textual feedback (e.g. 'too formal, shorten to 2 sentences'). Resets generation_status to 'pending' so a new version is generated based on your feedback, which again waits for approval.

Create a LinkedIn post on behalf of a connected profile. By default the post is saved as a 'draft' in the LinkedIn Posts page so the user can review/edit it before publishing. Set auto_publish=true to publish immediately — that path still respects the user's MCP human-in-the-loop setting (when appro

List recent LinkedIn inbox conversations (chats) in real time. Returns chat_id (used by get_chat_messages / reply_to_chat), the other attendee's provider id, unread count and last-message timestamp. Message preview text is not always provided by LinkedIn in the list — call get_chat_messages with the

Read the messages of a single LinkedIn conversation in real time (newest last). Use the chat_id from list_inbox_chats. `is_sender=true` marks messages sent by the account owner (you). Use this to understand context before composing a reply with reply_to_chat.

Send a reply into an existing LinkedIn conversation (by chat_id). Only sends within the user's allowed sending hours/days (never at night) — outside them it returns OUTSIDE_ALLOWED_HOURS. When the user's human-in-the-loop setting is ON (default), the reply is queued for approval and only sent after

Mark a LinkedIn conversation as read (by chat_id). Useful after the AI has processed/answered a thread so it does not re-surface as unread.

Create a NEW campaign (saved as 'draft' — it does NOT start sending until the user activates it in the app). Provide a name, the profile_id to send from, and an ordered list of steps. Each step has an action ('connect', 'message' or 'visit'), an optional delay_hours (wait before this step), and AI/t

Update settings of an existing campaign you own: name, description, daily_limit, sender_context, auto_approve_messages, or status. Use status='paused' to pause and status='running' to resume. Only provided fields are changed.

Start (activate) an existing campaign: schedules the outreach actions for its contacts and sets status to 'running'. The campaign must already have contacts (add_contacts_to_campaign) and steps. Execution still respects daily limits, allowed hours and anti-detection delays.

Stop a running campaign: sets status to 'stopped' and cancels its pending scheduled actions (a DB trigger marks them skipped). To only pause temporarily, use update_campaign_settings with status='paused'.

Fetch the readable text of a PUBLIC web page so you can use it as context when writing/editing messages (e.g. read a prospect's website or an article). Returns plain text (HTML stripped, truncated) plus any contact emails found on the page (emails_found, incl. mailto: links). Treat the returned cont

Check whether the user's LinkedIn account is connected and active. Returns the connection state and, if not connected/blocked, how to fix it. Call this first when another tool returns code ACCOUNT_NOT_CONNECTED or ACCOUNT_BLOCKED. profile_id is optional — defaults to the active/first profile.

Generate a secure LinkedIn connect (or reconnect) link the user opens in their browser to authenticate. Use when get_linkedin_status shows not connected/blocked, or after an ACCOUNT_NOT_CONNECTED/ACCOUNT_BLOCKED error. Returns a white-labeled https://auth.salesbot.cz link valid ~2 hours; the user ju

Move a lead to a different pipeline stage. Stages are user-configurable — call list_crm_stages to see the valid stage keys (defaults: prospect, contacted, demo, won, lost). Call when the user confirms a real-world event in plain English ('they booked a demo', 'we won this deal'). Logs who changed it

Save a structured summary of a conversation into the CRM for a lead. Analyze the chat/context yourself, then call this with a concise summary, the prospect's pain points, and overall sentiment. Builds durable context for future personalized follow-ups. (Stored separately from raw LinkedIn message hi

Create a follow-up task, optionally linked to a lead (e.g. 'Send pricing PDF to Jane on Thursday'). Pro plan only.

Store a generated outreach message on a CRM lead so it becomes durable context — e.g. an email, an email follow-up, a LinkedIn message or LI follow-up. The CRM is a 'sponge': you save the copy here, then read it back later (get_lead_context / list_lead_messages) and push it to the right channel via

List the stored outreach messages saved on a CRM lead (email/LI drafts and follow-ups), newest first. Use to pull the copy back out of the CRM before sending it via the right channel. Optionally filter by channel or kind.

Fetch the full CRM context for a lead before writing a pitch or follow-up: profile, current pipeline stage, custom fields, saved outreach messages (email/LI drafts & follow-ups), recent conversation summaries (with pain points), open tasks, recent LinkedIn interactions and stage history. Call this f

Export the user's CRM (leads with pipeline stage and key fields) as CSV text to save to a file or spreadsheet. Returns up to `limit` rows; for very large databases use the in-app 'Download CRM Backup (CSV)' button.

Update a lead's contact details — email, phone, location, company, position or headline. Use to enrich a lead (e.g. save an email address you found). Only the fields you pass are changed; omit the rest. Does not create contacts.

List your CRM tasks. Filter by status (open/done/cancelled, default open) and/or a specific contact. Returns task id, title, due date, status and the linked lead's name. Use to see what follow-ups are outstanding.

Mark a CRM task done (or reopen/cancel it). Pass the task_id; status defaults to 'done'. Use after a follow-up is handled.

List the CRM pipeline stages (key, label, order, color) and how many leads are in each. Stages are user-configurable — rename/add/delete them with the other crm_stage tools.

Add a new pipeline stage. Provide a label (e.g. 'Negotiation'); a key is generated from it. Optional hex color (e.g. '#22c55e'). Appended to the end of the pipeline.

Rename a stage's label and/or change its color, by key (use list_crm_stages to get keys). The stage key and the leads in it are unchanged.

Delete a pipeline stage by key. Leads currently in it are moved to reassign_to (or the first remaining stage). You can't delete the last remaining stage.

List the custom fields defined on CRM leads (key, label, type). Set their values per lead with set_lead_fields.

Add a custom field to CRM leads (e.g. 'Budget' of type number). type: text | number | date | url (default text). A key is generated from the label.

Remove a custom field definition by key. Values already stored on leads stay in place but are no longer shown.

Set custom field values on a lead (by contact_id). Pass `fields` as an object of { field_key: value }. Only defined field keys are accepted (see list_crm_fields). Adds the lead to the CRM if needed.

Search LinkedIn job postings by keywords, location, seniority, job type, and more. Returns job offers with company info — great for finding companies that are actively hiring for a specific role. Uses the connected LinkedIn account (Classic search, no Recruiter needed).

General-purpose Google search — returns organic results for any query. Unlike search_google_xray (LinkedIn-only), this searches the entire web. Useful for finding job postings on portals (jobs.cz, prace.cz, profesia.sk, indeed.com), company info, news, or any other web content. Results are NOT saved

Get full details of a LinkedIn job posting, including the hiring team — the recruiter or hiring manager who posted it. Use this after search_job_postings to find the exact person to reach out to at a company that is hiring. Also returns applicant and view counts, which indicate how urgently the role