MCP server
The Lead Scorer MCP endpoint, how it authenticates, which clients it works with, and the full list of capabilities grouped by family.
Agents & MCP · Last updated
On this page
Lead Scorer was built AI-first: every feature ships as an MCP tool rather than as a bolted-on integration. Anything you can do in the app, an agent you control can do over the protocol, with the same credits, the same billing and the same approval gate before anything sends.
Endpoint and authentication
list_billing_invoices reads the authenticated account's issued invoices with private PDF download links. Pass next_cursor as cursor to load older pages without a date cutoff. It is free, read-only and does not send email or start a payment.
https://mcp.lead-scorer.com/mcp
- OAuth 2.1 is the recommended authentication, with a setup screen in the app that walks you through it.
- An Authorization: Bearer header with an MCP API key works as a manual fallback for clients without OAuth support.
- Included on every plan, free CRM included.
Supported clients
Claude (custom connectors), Claude Code, ChatGPT (developer mode), Codex, Cursor, or any MCP client you write yourself. Per-client setup instructions, with the exact commands and JSON, live on the MCP page. They are kept in one place on purpose.
- Set up your client
Step-by-step configuration for Claude, Claude Code, ChatGPT and Cursor.
Set campaign priority to High, Normal or Low directly in the campaign list, or use update_campaign_sending with priority: high, normal or low. Read it back with list_campaigns or get_campaign. Priority allocates each shared account budget without raising safety caps. Eligible campaigns retain one daily slot when capacity permits; otherwise minimum slots rotate each UTC day. Paused campaigns and campaigns without eligible work release their share. Within a priority, existing follow-up and due-date ordering remains. Set daily_invite_limit to null to restore the inherited account limit.
Daily event invitation campaigns
From Campaigns → Invite to event, or Event campaign on a lead list, choose your list, LinkedIn event, connected account, daily limit, sending days and timezone. Creation takes a fixed snapshot of accessible leads and leaves every invitation for review. Activate in the campaign page to start the daily queue; pause and resume there. No invitations or credits are spent at creation.
With MCP, discover IDs using get_lead_lists and list_sender_accounts, then call create_event_invite_campaign with list_id, linkedin_account_id, event_url and a stable idempotency_key. The default is up to 100 event invitations daily, seven days a week, 09:00–18:00 Europe/Paris. Use update_campaign_sending to change daily_event_invite_limit, days or hours. Human activation remains in the app. Inspect results with get_campaign and list_campaign_actions.
Event invitations have their own budget, independent of connection requests and messages. The account ceiling is shared with manual invitations and other campaigns and resets at midnight UTC; send windows use your chosen timezone. Already invited members are skipped across URL/ID variants, campaigns and manual sends. Missing member IDs are looked up from the LinkedIn profile at delivery and saved for reuse. Temporary lookup failures wait for a retry without sending; unresolvable profiles fail with a reason. The daily limit is a maximum: available contacts, sender availability and the sending window can reduce actual sends.
For a LinkedIn event invitation campaign, use Refresh registrations to measure registered people among unique invitees with confirmed sent invitations. The campaign list and detail show this rate, counts, last update and registered invitees. Refresh is manual only: no scheduled synchronization, no daily refresh quota and no credits charged. Until the first refresh, the metric is Not refreshed; no invitations means no rate. A failed or incomplete refresh preserves the last successful snapshot. The denominator is fixed when the refresh starts. LinkedIn visibility limits apply; this measures registration, not direct acceptance of our invitation or attendance. get_campaign reads the cached analytics.event_registrations without initiating a refresh.
Each lead's Event registrations section keeps dated observations from event audience imports and successful campaign refreshes, including external events. It can show several events for the same prospect. These records are private to your workspace and do not prove attendance or current registration. Opening a profile only reads saved data. MCP get_lead returns event_registrations with items and total; use event_offset to read the next 100 observations. Historical imports are included only when explicit event provenance was saved; list membership alone is not evidence.
Recruitment signals and company associations
Discover companies with search_companies or get_companies_from_list and create only missing companies. Associate each lead using company_id at creation, or enrich and read get_lead.positions before set_lead_primary_company. The company must belong to that person's career; never guess IDs or treat a parent as the recruiting subsidiary. Pinning survives later enrichment.
First read list_hiring_taxonomy (kind=role, skill or seniority; paginate until has_more=false) to discover the global canonical vocabulary. Reuse its slugs; ensure_hiring_term registers a genuinely missing generic term or reuses an existing label/alias, case-insensitively. The catalog exposes no companies or usage counts. Record a verified public vacancy with upsert_company_hiring_signal (job title, location, URL, open/closed/unknown status and observed_at). Use details to retain salary (currency and period only when stated), work mode, remote policy, profile criteria, stack, responsibilities, benefits, interview stages and dated sources. These appear in the company’s existing Open Positions section and full vacancy dossier. Omitted detail fields survive later refreshes; explicit null clears a field. posted_at is optional: do not confuse verification and publication dates; keep relative dates in details.publication_label. Repeated company + source URL updates the same signal, and older observations cannot replace fresher evidence. Read back get_company_signals and get_lead to verify the company page and CRM association. Pass normalized.roles, normalized.skills and normalized.seniorities as arrays of {slug,evidence}, quoting the title or relevant saved details verbatim. Unknown slugs and absent evidence are rejected; duplicate references collapse to one canonical tag. All arrays replace the selection; empty arrays mean none, omission keeps an existing selection, and normalized=null restores automatic extraction. Legacy/provider imports also resolve their tags through the global catalog. Original source text can retain its original casing. Seniority is separate from role and is never inferred from years of experience alone. Use search_hiring_companies or the Companies hiring filters for role + skills + seniority + location; every criterion must match one vacancy. Open unexpired offers are the default; status=all includes historical needs, and observed_since filters verification freshness. The index preserves source evidence and groups aliases such as Postgres/PostgreSQL. These are detected vacancy needs, not proof of company-wide technology adoption. These operations are free and neither enroll nor contact anyone; keep private candidate and outreach details in private memory.
Freelance talent pool
From Agents, open Find freelance talent in ChatGPT, Codex, Claude or Claude Code. It follows the same native research architecture as Find hiring companies: your assistant searches the CRM first, confirms the distinct-person target and mandatory criteria, then opens public individual profiles and saves verified facts with the existing CRM tools. Each new run creates exactly one lead list for all sources; continuation reuses that same list. Provider names and URLs remain on the profiles. It reports partial results, inaccessible sources and missing or stale evidence. Mandatory availability, mobility and rate requirements need explicit current proof; a residence or a rate minimum alone does not prove a match. No backend discovery workflow or campaign is started.
Freelancers remain normal CRM leads, so lists, tags, contact details, experiences and relationship memory continue to work. A structured freelance profile adds availability and its verification date, available-from date, daily-rate range and currency, years of experience, notice period, work modes, contract preferences, locations, languages, industry experience, portfolio or CV links, a recruiter summary, normalized roles/skills/seniorities, and dated public source observations. The same global vocabulary prevents Python/python duplicates across vacancies and candidates.
Use search_freelancers before new research and filter by canonical role, all required skills, seniority, availability date, maximum rate, currency, work mode, location, source or owned lead list. Pass lead_id to upsert_freelance_profile for an existing CRM contact. If a named platform profile has no LinkedIn or public email, pass identity instead: the exact source URL creates or reuses the lead and run-list membership atomically, without merging on name alone. Each normalized term needs a verbatim excerpt from the lead or supplied source. Availability, rates and experience stay unknown unless explicitly published. Older observations remain visible but cannot overwrite fresher facts. Read get_freelance_profile to audit every source. These operations are free and send nothing.
Contacts without LinkedIn
Create a contact with an email, a verified LinkedIn identity, or a full name and an authorized company_id. An email-only company mailbox can omit full_name; contact_kind=company keeps personalization neutral. In Imports, Contacts CSV accepts email, company_name, company_website, country, preferred_language and optional full_name or LinkedIn identity. Preview errors and retry completed batches safely: normalized email deduplication is scoped to your account.
In a mixed campaign with an email branch, recipients without LinkedIn start with the reachable email step once approved, paced by the sending schedule. No invitation is recorded as sent. Recipients with LinkedIn retain the normal invitation and acceptance deadline. Follow-ups wait for the preceding email to send, and the two connection branches remain exclusive. LinkedIn enrichment without a usable identity and without cached profile data makes no provider call and consumes no credits; the run records the non-applicable reason.
Capabilities by family
The surface is grouped by capability family. Tool names are stable and are what your agent will see when it lists the server.
Audience capture accepts LinkedIn post links, including shared links and embed URLs. Shared posts are resolved through LinkedIn's public embed metadata. If that lookup fails, capture uses one of your connected LinkedIn accounts to resolve the post; linkedin_account_id can select the account. The fallback requires an active connection and available LinkedIn read quota. Reactions and comments are then collected using the resolved activity ID. Large post audiences continue automatically in batches of up to 1,000 profiles, saving reaction and comment progress separately. Re-sync resumes an unfinished capture; after completion, it starts a fresh scan for new engagers.
Connection degrees are specific to a LinkedIn account. Captures save degrees already returned by the provider without extra calls, including observations for leads already in your list. Select an account in a lead list to view saved degrees, filter first-degree or second/third-degree leads, then use the existing list and campaign actions to split one captured audience. Missing evidence remains unknown. Reading or filtering saved degrees never triggers a LinkedIn lookup. get_lead and get_leads_from_list accept linkedin_account_id; list reads also accept connection_degrees and connection_degree_unknown.
The capture form shows relevant controls after recognizing a LinkedIn URL. People searches show their scan limit and required account immediately; post captures show the engagement type and target list. Open Advanced settings for connection-degree search filters, optional degree lookups and pre-qualification. Lookup limits appear only when enabled. Active filters and enabled options remain summarized when Advanced settings is collapsed. Switching source type clears optional read consent and search filters, so a new capture cannot inherit hidden options that consume additional reads.
Optional missing-degree lookups are disabled by default. Enable them in Capture settings or pass refresh_missing_degrees=true when creating or updating an audience source. Choose the connected LinkedIn account, including for post captures, and a degree_lookup_limit from 1 to 1,000 additional reads per run (default 100). When enabled, the form and estimate show the upper bound before capture; each attempted lookup uses the existing capture read allowance and no extra credits. Saved degrees are reused. Limits, account restrictions and lookup failures leave partial results visible and unresolved degrees unknown. Changing settings does not launch a refresh: re-sync explicitly to recover historical missing degrees. People-search captures can also apply degrees before fetching; unsupported opaque Sales Navigator URL overrides are rejected rather than silently scanning a wider audience.
When an invitation-led campaign includes leads already connected to its sender, preflight warns with the affected leads so you can review follow-up wording before activation. Redundant invitations are skipped while approved follow-ups remain available. For an old connection, the configured follow-up delay starts when the invitation is bypassed in this campaign. For a newly accepted invitation, the delay still starts at acceptance. Opening preflight and correcting these deadlines do not add LinkedIn API reads.
People-search captures default to scanning 100 profiles per explicitly authorized batch. Set max_profiles from 10 to 1,000 in multiples of 10 in the capture form or source settings. The limit counts raw provider profiles, including duplicates and people already in your lists, across automatic continuations and daily quota resets. It does not count only newly imported leads. Capture stops at the scan limit and does not automatically start another batch. Capture more shows the next scan limit and shared daily allowance before you confirm; it resumes saved progress and authorizes another batch. Changing max_profiles in settings only affects the next explicitly authorized batch; scan_limit keeps the current batch allowance unchanged during automatic continuations. Classic LinkedIn search pages contain 10 profiles, so capture stops before a page would exceed the remaining limit. Optional missing-degree lookups have their own additional-read limit and use the same daily allowance; the estimate shows capture_reads_upper_bound separately from additional_reads_upper_bound. Estimation itself still reads at most one preview page.
Capture quotas are separate from campaign reads. list_sender_accounts reports confirmed, uncertain and reserved capture reads, remaining allowance, total reads and UTC reset. estimate_audience reads at most one search page without creating a list or spending enrichment credits; an unavailable total is unknown, not zero. Captures run in a strict queue per account. Use pause_audience_source, resume_audience_source and reorder_audience_sources to manage pending captures; delete_audience_source keeps the list and leads and requires confirmation. Active captures cannot be paused or deleted. update_sender_account can set linkedin_daily_capture_read_limit from 1 to 10,000, or null to inherit the global safety setting. Classic people searches require 10 available reads per page. Higher settings increase restriction risk and do not bypass LinkedIn per-query result caps. Timeout results preserve captured pages and distinguish uncertain reads from exhausted quota.
- CRM read
- get_lead · get_leads_from_list · get_lead_lists · get_company_info · get_company_signals · list_hiring_taxonomy · search_hiring_companies · search_freelancers · get_freelance_profile · get_companies_from_list · get_company_lists · search_companies · list_tags · list_products · list_sender_accounts
- CRM write
- create_lead · update_lead · set_lead_primary_company · ensure_hiring_term · upsert_company_hiring_signal · upsert_freelance_profile · remove_lead_access · create_company · create_list · create_product · update_product · delete_product · add_leads_to_list · add_companies_to_list · add_tags_to_lead · add_lead_email · add_lead_phone · update_lead_linkedin · update_company_linkedin
- Sourcing & audiences
- create_audience_source · list_audience_sources · sync_audience_source · estimate_audience · pause_audience_source · resume_audience_source · reorder_audience_sources · delete_audience_source · fetch_profile_posts · get_lead_posts
- Contact lookup estimates
- Use find_lead_contact_info with dry_run: true to check access, eligible lead data, active-run limits and provider configuration before spending. No mailbox connection is required for discovery. A successful estimate does not guarantee live provider availability. Launch once, then poll get_contact_enrichment_run; only contacts found are billed.
- Verify emails already in your CRM
- Discover the lead with get_lead_lists and get_leads_from_list, then call verify_lead_emails with lead_id and dry_run: true. This checks access, visible emails and provider configuration for free. Execution costs 1 credit per successful lead verification, regardless of email count; failures are refunded. Respect the confirmation threshold. It does not search for new contacts. Read verification_status, verification_provider and verified_at with get_lead; re-running verification is a new paid operation. Missing email access, no visible emails, insufficient credits and provider failures are reported explicitly.
- Enrichment & scoring
- enrich_leads · enrich_company · find_lead_contact_info · verify_lead_emails · create_scoring_config · submit_lead_score · submit_lead_ai_enrichment · submit_company_classification · submit_company_research · get_leads_pending_scoring · get_leads_pending_ai_enrichment · get_companies_pending_classification · get_companies_pending_research
- Campaigns & outreach
- list_sender_accounts · update_sender_account · list_campaigns · create_campaign · create_event_invite_campaign · update_campaign_sending · update_campaign_senders · get_campaign · get_campaign_authoring_context · add_leads_to_campaign · list_campaign_leads · remove_lead_from_campaign · add_campaign_step · update_campaign_step · preview_campaign_step_deletion · delete_campaign_step · cancel_campaign_action · reopen_campaign · update_campaign_mode · preview_campaign_close · close_campaign · preview_campaign_draft_review · review_campaign_drafts · generate_campaign_drafts · write_campaign_drafts · list_campaign_actions · update_campaign_action_draft · upload_campaign_action_attachment · delete_campaign_action_attachment · invite_list_to_linkedin_event
- Follow-up & agenda
- get_agenda · get_lead_followup · start_opportunity · list_interactions · log_interaction · add_transcript · get_transcript · submit_transcript_insights · list_tasks · create_task · update_task · list_calendar_events · find_free_slots · link_calendar_event · create_lead_from_calendar_attendee · create_calendar_event · update_calendar_event · cancel_calendar_event
- Analyse calls with your own AI
- Lead Scorer never analyses a transcript itself. Save the text with add_transcript, read it with get_transcript, and let your AI write the summary, objections, facts and next steps with submit_transcript_insights. Next steps arrive as suggested tasks that you accept or dismiss; durable facts about the person go to relationship memory with remember_relationship_fact.
- Meetings in your calendar
- The agenda reads the Google or Outlook calendar of the mailbox connected as your email channel and links meetings to your prospects. find_free_slots proposes times; create_calendar_event, update_calendar_event and cancel_calendar_event send real invitations or cancellations, so your agent calls them with confirm: true only after you approve the exact meeting.
- Keep a campaign open
- A one-shot campaign completes once every message is resolved. Make it permanent in its sending settings, or with update_campaign_mode, to keep it live and waiting for new recipients when its queue empties. A completed campaign can be reopened from its page or with reopen_campaign: it comes back paused with its full history, and nothing is sent until you resume it. New recipients still need their own approved message, through the review screen or preview_campaign_draft_review then review_campaign_drafts. Close it any time from the More menu or with close_campaign.
- Remove a campaign lead
- In a campaign's Leads tab, choose Remove and confirm. From MCP, discover the campaign with list_campaigns and the lead with list_campaign_leads, then confirm remove_lead_from_campaign using lead_id. Removal deletes the enrollment, drafts, actions and replies while keeping the CRM lead. Removing CRM access, individually or in bulk, also clears the lead from your campaigns. Sends already in progress or with an unknown outcome must be resolved first.
- Content Studio
- create_content_post · update_content_post · schedule_content_post · archive_content_post · mark_content_post_published · list_content_posts · get_content_calendar · list_content_items · get_content_item · upsert_content_item · update_content_item · list_content_shows · upload_content_media
- Engagement (LinkedIn, X and Reddit)
- list_engagement_watches · upsert_engagement_watch · search_linkedin_posts · add_linkedin_post · list_pending_engagement_posts · list_ready_engagement_cards · get_engagement_card · follow_engagement_author · follow_engagement_subreddit · get_engagement_post_comments · submit_engagement_reviews · save_engagement_invite_note · get_engagement_results
- Review LinkedIn, X and Reddit posts with your own AI
- Engagement watches collect LinkedIn posts by persona, three times a day, through your own LinkedIn account and within its daily post budget; they never cost credits. Your AI (Claude or ChatGPT) reads the waiting posts with list_pending_engagement_posts, reads your voice in get_my_memory, and saves a verdict and three comment angles per post with submit_engagement_reviews. No tool publishes, reacts or dismisses: you pick an angle and publish it, or dismiss the post, in Content › Engagement. To hear which posts to comment today and the comments proposed, ask your AI: list_ready_engagement_cards reads the ready cards in the order of the queue, with their angles and where each one is published (the LinkedIn post, X's prefilled reply, the Reddit thread), and get_engagement_card reads one card; both only read. Each author your AI keeps joins your CRM list for that network (Engagement · LinkedIn, Engagement · X or Engagement · Reddit). Once you agree, follow_engagement_author adds a LinkedIn or X card's author to its watch, and follow_engagement_subreddit adds a subreddit a Reddit watch suggests after two posts kept; each followed account or subreddit adds reads on every run, so nothing is followed without your consent. get_engagement_results shows which watches, post types and links bring replies, conversations and sign-ups. It is opening account by account during the pilot: until then, creating or running a watch answers that it is not open yet. An X watch (network x) reads public X posts: a search query, followed X accounts and X lists, without any account of yours and within a daily allowance of X post reads. X refuses replies sent by an app, so you always post the reply yourself: Content › Engagement opens X with your reply already written. X watches open account by account, separately from LinkedIn. A Reddit watch (network reddit) reads public Reddit posts: the subreddits you follow first, then a search query, without any account of yours and within a daily allowance of Reddit post reads. Reddit search is loose, so Lead Scorer only keeps the searched posts whose title or text match your whole query. Your AI writes comments that answer the question asked, without a link or a pitch. No Reddit link fills in a comment: Content › Engagement copies it and opens the thread, you post it yourself, and nothing is ever voted for you. Reddit watches open account by account, separately from LinkedIn and X.
- Agent workflows
- list_workflows · get_workflow_run · list_workflow_runs
- Personal memory & Context Packs
- get_my_memory · get_my_workspace_context · update_my_memory · list_relationship_memories · get_relationship_memory · update_relationship_memory · remember_relationship_fact · archive_relationship_memory · list_company_memories · get_company_memory · update_company_memory · remember_company_fact · archive_company_memory · list_memory_revisions · list_memory_sources · get_memory_source · archive_memory_source · list_pending_memory_sources · submit_memory_facts · compile_context_pack · list_memory_proposals · review_memory_proposal · review_memory_proposals
Credits over MCP
AI-powered tool calls consume the same credits and the same AI budget they would in the app. There is no cheaper back door and no separate quota to track.
Lumail event reminder campaigns
From a lead list, choose Event Reminder campaign to create email reminders at your chosen times before your own LinkedIn event. Start with 7 days, 1 day and 1 hour, or add, remove and edit reminders, such as 15 minutes before. Choose 1–10 different timings, between 1 minute and 30 days before the event. MCP messages use integer offset_minutes; legacy integer offset_hours remains accepted instead, never both on one message. An event starting in 20 minutes can have a 15-minute reminder. At least one reminder must still be in the future when creating and activating the draft. Only recorded registrants with accessible usable emails are included; confirm their permission, review the fixed audience, sender, messages and exact times, then activate in the app. Pause or cancel there. Past slots are skipped. To change the event time or content, cancel and create a new draft. Lumail credentials and a verified sender must be configured for your workspace. Accepted means queued by Lumail, not inbox delivery. MCP supports list_event_reminder_campaigns, create_event_reminder_campaign and get_event_reminder_campaign; activation stays in the UI.
Event reminder campaigns require the event-reminder-campaigns PostHog feature flag. It gates navigation, direct routes, API/MCP access and queued delivery. Missing or failed evaluations keep the feature disabled, including for administrators. Recipient unsubscribe links continue working when the flag is off.
Before every scheduled reminder, Lumail verifies the exact recipient email. Only a completed, accepted check allows sending. Rejected addresses are skipped; incomplete checks, quota exhaustion and temporary errors never bypass verification and retry only within the reminder’s delivery window. Suggested addresses are not substituted. Creation and reads remain free of provider calls; verification uses the Lumail organization’s quota.