CLI and MCP server for the LinkedIn API
Connect Runs on your machine
claude mcp add linkedctl -e LINKEDCTL_ACCESS_TOKEN=<LINKEDCTL_ACCESS_TOKEN> -e LINKEDCTL_CLIENT_ID=<LINKEDCTL_CLIENT_ID> -e LINKEDCTL_CLIENT_SECRET=<LINKEDCTL_CLIENT_SECRET> -- npx -y [email protected]{
"mcpServers": {
"linkedctl": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"LINKEDCTL_ACCESS_TOKEN": "<LINKEDCTL_ACCESS_TOKEN>",
"LINKEDCTL_CLIENT_ID": "<LINKEDCTL_CLIENT_ID>",
"LINKEDCTL_CLIENT_SECRET": "<LINKEDCTL_CLIENT_SECRET>"
}
}
}
}{
"mcpServers": {
"linkedctl": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"LINKEDCTL_ACCESS_TOKEN": "<LINKEDCTL_ACCESS_TOKEN>",
"LINKEDCTL_CLIENT_ID": "<LINKEDCTL_CLIENT_ID>",
"LINKEDCTL_CLIENT_SECRET": "<LINKEDCTL_CLIENT_SECRET>"
}
}
}
}{
"servers": {
"linkedctl": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"LINKEDCTL_ACCESS_TOKEN": "<LINKEDCTL_ACCESS_TOKEN>",
"LINKEDCTL_CLIENT_ID": "<LINKEDCTL_CLIENT_ID>",
"LINKEDCTL_CLIENT_SECRET": "<LINKEDCTL_CLIENT_SECRET>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
LINKEDCTL_ACCESS_TOKENRequired, secret | LinkedIn OAuth2 access token |
LINKEDCTL_CLIENT_IDOptional | LinkedIn OAuth2 client ID |
LINKEDCTL_CLIENT_SECRETOptional, secret | LinkedIn OAuth2 client secret |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 10 Mar 2026 |
| Last updated | 10 Mar 2026 |
| Registry name | io.github.alexey-pelykh/linkedctl |
More marketing and seo servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.