Connect Claude to your LinkedIn CRM with MCP
Swimlane ships an MCP server: point Claude, Cursor or the OpenAI API at your workspace and ask for the work instead of writing the calls. Setup, five real examples, and the guardrails.
Team & API
Contacts, lists and tags are shared across the team. A digest recaps what everyone did, and the API and webhooks push warm contacts wherever you work.
Shared contacts, lists and tags, and a digest of what each member did — so the team works from one record, not five spreadsheets.
A daily or weekly email of what the team did: invitations sent and accepted, messages sent, and how each campaign performed.
REST endpoints for contacts, lists and companies, scoped tokens, and a Swagger reference you can read right now.
Read the API docsPush a warm contact into your CRM, your warehouse or a Slack channel through n8n, Make or a webhook — no glue code.
Browse integrationsKeep reading
Swimlane ships an MCP server: point Claude, Cursor or the OpenAI API at your workspace and ask for the work instead of writing the calls. Setup, five real examples, and the guardrails.
Swimlane's public API covers the whole loop: import contacts from LinkedIn, work them in the CRM, build and run campaigns. A tour with the calls that matter and the traps worth knowing.
The webhook contract Swimlane sends, how to verify and retry it, and receiver patterns for HubSpot, Salesforce and Pipedrive via n8n, Make or your own code.
A LinkedIn reply belongs in your CRM. Your campaign tags whoever replied; a scheduled n8n or Make workflow reads the tag through the API and opens the deal.
Connect LinkedIn in two minutes. Free to start, and free to leave with your data.
7 days free · Cancel anytime