One LeadAdapter workspace API key connects LinkedIn research, prospect knowledge, native CRM and the workflows around them. Choose an SDK workflow or connect your assistant to the remote MCP service.
Create or sign in to LeadAdapter · Plans and pricing · API reference
Pending ingestion stays resumable. Private checkpoints retain stable request keys; uncertain writes hold for reconciliation rather than replaying.
The Node and Python SDKs offer ergonomic resources on the existing REST API, retain their low-level request methods, and include a no-network plan plus source-shaped fixture workflow.
node lib/cli.mjs workflows research-to-crm --fixture
python3 -m leadadapter workflows research-to-crm --fixtureRun the Node command from the matching Node SDK release and the Python command from its installed wheel/source package. Fixture mode stops for review before writes.
The current bridge initializes LeadAdapter’s remote MCP endpoint at https://leadadapter.com/mcp, discovers its actual tools, and forwards calls under your scoped workspace key. Tool names and availability come from the remote service.
export LEADADAPTER_API_KEY="YOUR_WORKSPACE_API_KEY"
node lib/cli.mjsRun from the matching linkedin-mcp release. node example.mjs --live lists remote tools only; discovery does not prove a LinkedIn operation ran.
linkedin-api · linkedin-typescript-sdk · linkedin-python-sdk · linkedin-mcp
Matching SDK releases bundle task skills for Codex, Claude and Grok. Use the supported installer with explicit project scope:
node lib/cli.mjs agents install --client codex --scope project --project /path/to/project
python3 -m leadadapter agents install --client claude --scope project --project /path/to/projectProject-local guidance belongs under .agents/skills or .claude/skills as supported by the chosen client. Installing skills grants no credentials or write approval. Check each repository’s current release assets and README for the agentkit included in that version.
| Task | Resources |
|---|---|
| Research | people.search · profiles.enrich · posts.engagers |
| Knowledge and selection | prospects.list · prospects.get |
| Approved native CRM | prospects.promote · leads.list · leads.export |
| Explicit external CRM | crm.sync_lead with a named connected provider |
| Jobs | jobs.wait; terminal failures are not completed research |
Selected operation IDs and prerequisites are recorded on the task pages. Full response data follows the API envelope; the SDK does not invent universal provider profile/result schemas.
Run focused people research, wait for completed results, match exact stored prospect identities, then explicitly approve native LeadAdapter CRM promotion. External CRM sync requires a named provider and separate approval.
Explicit access and review gatesSearch people using explicit keywords, follow the returned job receipt and inspect completed results before using them in another workflow.
Explicit access and review gatesRequest available profile context for a known LinkedIn URN, public profile ID or captured lead. Preserve source identity and inspect actual coverage.
Explicit access and review gatesRequest post-engager information available to the connected account, then review exact identities before qualifying prospects.
Explicit access and review gatesRead workspace-scoped leads, apply documented filters and paginate the API export into your own destination mapping.
Explicit access and review gatesRead existing content and scheduled post states, then use documented write operations when an approved publishing workflow is needed.
Explicit access and review gatesRead pending approvals and action audit records, then decide specific proposals through the documented governance workflow.
Explicit access and review gatesInspect configured webhook subscriptions and delivery history, then configure an authorized signed-event receiver using the API reference.
Explicit access and review gatesUse only your LeadAdapter workspace key. Fresh LinkedIn research needs a connected supported execution mode, required consent and applicable plan allowances. Reads use their documented read scope; promotion and external sync need write access and explicit approval.
The public SDK and bridge code connect to LeadAdapter’s private hosted service. They do not include its backend. SDK fixture tests establish client behavior. MCP initialization/tools-list tests establish protocol discovery. Neither establishes live provider execution, native promotion or external delivery.
PipMCP gateway clients use their own PIPMCP_API_KEY and hosted provider connections. LeadAdapter continues to use its separate workspace key. Historical local PipMCP proof does not establish current hosted results.