CLI and MCP server for the LinkedIn API
CLI and MCP server for the LinkedIn API. That is what the linkedctl mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
OAuth2 CLI and MCP server for the LinkedIn API.
The server publishes 8 tools. What each one is for:
Authentication — The Authentication tool exposed by this serverPosts — The Posts tool exposed by this serverComments — The Comments tool exposed by this serverReactions — The Reactions tool exposed by this serverOrganizations — The Organizations tool exposed by this serverAnalytics — The Analytics tool exposed by this serverMedia — The Media tool exposed by this serverProfiles — Profiles let you manage multiple LinkedIn accounts or configurations. Each profile is stored as a separate YAML file under ~/.linkedctl/:Installation goes through your MCP client rather than a global install: point it at linkedctl on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: YOUR_CLIENT_ID, YOUR_CLIENT_SECRET, YOUR_ACCESS_TOKEN, YOUR_REFRESH_TOKEN, YOUR_TOKEN, LINKEDCTL_CLIENT_ID, LINKEDCTL_CLIENT_SECRET, LINKEDCTL_ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Linkedctl's toolset — Authentication, Posts, Comments and 5 more — is a fair guide to whether it matches your workflow. It is maintained by alexey-pelykh; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Authentication | The Authentication tool exposed by this server. |
| Posts | The Posts tool exposed by this server. |
| Comments | The Comments tool exposed by this server. |
| Reactions | The Reactions tool exposed by this server. |
| Organizations | The Organizations tool exposed by this server. |
| Analytics | The Analytics tool exposed by this server. |
| Media | The Media tool exposed by this server. |
| Profiles | Profiles let you manage multiple LinkedIn accounts or configurations. Each profile is stored as a separate YAML file under ~/.linkedctl/: |
{
"mcpServers": {
"linkedctl": {
"command": "npx",
"args": ["linkedctl", "mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| YOUR_CLIENT_ID | Configuration value read at startup. | Optional |
| YOUR_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| YOUR_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_REFRESH_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
| LINKEDCTL_CLIENT_ID | Configuration value read at startup. | Optional |
| LINKEDCTL_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| LINKEDCTL_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.