LinkedIn MCP

Search basic candidate profiles using explicit employer, title, location and native seniority filters. Choose one shared company search or independent company allowances. Full-profile and email discovery remain separate opt-in reads; a search does not verify responsibility or employment.

Find candidate company pages from website domains, discover companies through supported filters, or retrieve known company details. Associated-profile counts remain distinct from About-page size bands and payroll headcount. Every supplied target retains an outcome.

Search postings using an explicit query or list a known company's jobs by native ID. Retrieve a known posting's full description separately. Source limits and recency are explicit; capped results do not establish complete hiring activity.

Search posts, retrieve known posts and inspect bounded profile or company feeds. Available native content and provenance are retained. Reposts and original publication can have different dates; missing reaction-event timestamps remain unknown.

Collect bounded comment or reaction records for known posts. A preset can retrieve post details alongside selected audience datasets with separate budgets and recovery receipts. It does not automatically enrich people, rank prospects or interpret engagement as intent.

Use the result reader with the returned source tool and Apify run ID. It verifies the configured account, qualified Actor build and original recipe, then reads bounded saved rows. Pending runs can be observed later. A separate source cursor explicitly authorizes new paid acquisition.

Find candidate LinkedIn company pages for website domains. Ambiguous or missing matches remain unresolved; this paid lookup does not establish company identity.

Get LinkedIn-associated employee counts for known company pages. These are not payroll headcounts; unavailable values stay unknown. Collection costs money; use the result reader for pending or remaining results.

Search candidate employees at one known company using explicit filters. Returns basic profiles, not a complete roster or verified decision-makers. Paid collection; empty searches can incur start fees.

Search candidate employees across several companies under one shared limit; larger employers can crowd out smaller accounts. Returns basic profiles, not a complete roster or verified decision-makers. Paid collection; empty searches can incur start fees.

Retrieve one known profile’s identity and experience. Optional email discovery adds cost and may yield no address; profile retrieval does not independently verify employment.

Retrieve a bounded batch of known profiles, with a separate outcome for every input. Email discovery is off unless explicitly requested and adds cost; resume existing results instead of restarting the batch.

Search job postings across companies using an explicit query and optional location/recency. Matching can relax Boolean operators; inspect the posting evidence. Paid collection returns excerpts; read known jobs for full descriptions.

List jobs for a known company ID, with explicit source scope and a bounded paid result allowance. Results are excerpts and can be capped; they do not prove the company’s complete hiring activity.

Retrieve one known job posting with full description and supplied company details. Removed or unavailable postings have an explicit missing outcome. This is a paid read.

Search posts by an explicit query and supported author/date filters. Source matching is fuzzy; local term hits are evidence, not a relevance score. Paid collection; inspect the existing invocation after an ambiguous failure before retrying.

Retrieve known posts by URL with content and available engagement totals. Preserve a separate outcome for every URL. This paid read does not retrieve the full commenter or reactor audience.

List bounded original posts, quote posts and reposts from profiles. Activity dates can differ from original publication. Paid collection; the observed feed is not complete.

List observed comments made by profiles, including available underlying post context. Paid collection returns a capped history, not proof of all activity.

List observed reactions made by profiles and available post context. Reaction-event timestamps are unavailable, so this paid read does not establish recent engagement.

List bounded comments and their authors for known posts. Retain comment text and thread identity; capped comments do not equal all commenters or all nested replies. Paid collection.

List bounded reacting profiles and reaction types for known posts. A reaction is not buying intent; source audience limits apply. Paid collection; profile URL resolution never silently starts extra enrichment.

Discover basic candidate profiles without a company seed, using supported title, location, employer and seniority filters. Source pages are billable even when sparse; full-profile and email enrichment are separate opt-in reads. Candidate recent-change/posting flags are native fixed-window filters.

Discover candidate company pages using explicit keywords, location, industry and About-page size bands. Paid discovery returns basic companies; use company details for enrichment. Results are bounded and do not enumerate the whole market.

Retrieve full details for known company pages, including supplied website, industry, locations and employee facts. Paid batch returns an explicit outcome per company; size bands and associated-profile counts remain distinct.

List bounded company posts, with quote posts and reposts explicitly controlled. Paid collection excludes nested comments/reactions. This actor has no source-page continuation; only collected-result paging is available.

Search each supplied company independently with its own profile and spending allowance. More starts than shared search, but separate results, coverage and recovery per account. Explicit per-company budgets must fit the total authorized maximum before any launch.

Collect company facts plus explicitly selected employee, job or company-post datasets for known accounts. Return independent evidence and continuation; no fit score, narrative or automatic full-profile/email enrichment. Paid acquisitions have separate budgets that must fit the total maximum.

Collect known-post details and bounded comment/reaction datasets under explicit budgets. Preserve independent post/event provenance; the AI client owns cross-source overlap and lead qualification. Paid collection never silently enriches profiles or emails.

Observe an existing allowlisted LinkedIn collection and read a bounded page of its normalized results. Never starts another scrape. Requires current configured Apify account access; polling reports cumulative run charges rather than new collection spend.

No. Typenode calls selected third-party Apify Actors through Apify's API. It is not a LinkedIn API integration, and using an intermediary does not establish permission to collect or reuse data.

No. These tools retrieve data. They do not send messages, request connections, modify profiles or write to a CRM.

No. People discovery returns basic candidates. Email discovery is an explicit, separately priced option when reading known profiles, and it may return no address.

No. Counts describe LinkedIn-associated profiles, and reactions describe observed engagement. The toolkit supplies source evidence; your assistant or team decides how to interpret and qualify it.

Yes. Use its returned run receipt with the result reader. Reading an existing collection does not launch another Actor. After an uncertain launch failure, inspect the existing invocation and Apify run history before authorizing new collection.

Templates are included with Typenode. Each workflow that starts uses one run from your plan, including workflows called through your custom MCP connector. Third-party services may charge separately; see Apps and setup.

You choose which accounts to connect. The template’s workflows and tools use the access you configure. Review the required scopes and setup details before connecting an account.