LinkedIn account and stored-lead inspection

Inspect your connected profile state, then retrieve your workspace’s stored leads before planning further governed LinkedIn actions.

Documented Workflow definition · 2 real tool steps

Open LeadAdapter setup ↗

Prerequisites and sequence

Create a scoped LeadAdapter API key in your own workspace and keep it in the local client environment. API authentication and the connected LinkedIn profile are separate prerequisites; execution still depends on the enabled adapter, account access and owner consent.

get_extension_status_get — Extension status
list_leads_get — List Leads

The definition references existing connector operations in the order above. Individual-step evidence does not establish that the composed workflow has been executed successfully. Inspect each result before continuing, and explicitly authorize any write step.

Open provider authentication, permissions and all operations →

Run the local connector

Open source, with your own provider credentials. A LeadAdapter account and scoped API access are required. No PipMCP account is required for local execution.

git clone https://github.com/jannikco/linkedin-mcp.git
cd linkedin-mcp
npm ci --ignore-scripts
npm test
npm start

The default command shows the available operations offline. Provide LEADADAPTER_API_KEY through environment variables or the supported local OS-vault resolver.

For a stdio MCP client, launch npm run server in the checkout. Open the released connector for full client configuration →

Step inputs and operation evidence

get_extension_status_get

Extension status

GET /profiles

Read operation. Account authorization and provider rate limits still apply.

Local: Tested Managed: Documented

Inputs

Name	Type	Required	Description
`profile_id`	string	No	The LinkedIn profile to act as. Optional while the workspace has exactly one.

Operation sources: Source 1

list_leads_get

List Leads

GET /leads

Read operation. Account authorization and provider rate limits still apply.

Local: Tested Managed: Documented

Inputs

Name	Type	Required	Description
`search`	string	No	See provider documentation.
`status`	string	No	See provider documentation.
`page`	integer	No	See provider documentation.
`per_page`	integer	No	See provider documentation.
`profile_id`	string	No	The LinkedIn profile to act as. Optional while the workspace has exactly one.

Operation sources: Source 1

Run an authorized workflow

Supply records and parameters you are authorized to use, then execute the named steps through the released connector or your configured managed connection. A directory guide does not schedule or run these actions.

Open LeadAdapter setup ↗

Recorded public projects

linkedin-mcp