MCP server for LinkedIn's official API - create posts, manage events, and interact with LinkedIn through AI assistants
MCP server for LinkedIn's official API - create posts, manage events, and interact with LinkedIn through AI assistants. The linkedin mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
A Model Context Protocol (MCP) server that provides AI assistants with access to LinkedIn's official API. Create posts, manage events, and interact with LinkedIn - all through natural language via any MCP-compatible client.
Everything the assistant can do here goes through one of these:
linkedin_auth_start — Start OAuth 2.0 authentication flowlinkedin_auth_callback — Complete OAuth with authorization codelinkedin_auth_logout — Revoke token and log outlinkedin_get_my_profile — Get your LinkedIn profile (name, headline, photo, email)linkedin_get_my_email — Get your email addresslinkedin_get_auth_status — Check authentication statuslinkedin_get_rate_limits — View API rate limit usagelinkedin_create_post — Create text, article, or image postslinkedin_delete_post — Delete your postslinkedin_create_comment — Comment on postslinkedin_react_to_post — React to posts (like, celebrate, support, love, insightful, funny)linkedin_upload_image — Upload images for postsThe server ships on npm as npm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 4 environment variables: LINKEDIN_CLIENT_ID, LINKEDIN_CLIENT_SECRET, LINKEDIN_API_BASE_URL, LINKEDIN_AUTH_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. LinkedIn's toolset — linkedin_auth_start, linkedin_auth_callback, linkedin_auth_logout and 11 more — is a fair guide to whether it matches your workflow. It is maintained by souravdasbiswas; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| linkedin_auth_start | Start OAuth 2.0 authentication flow |
| linkedin_auth_callback | Complete OAuth with authorization code |
| linkedin_auth_logout | Revoke token and log out |
| linkedin_get_my_profile | Get your LinkedIn profile (name, headline, photo, email) |
| linkedin_get_my_email | Get your email address |
| linkedin_get_auth_status | Check authentication status |
| linkedin_get_rate_limits | View API rate limit usage |
| linkedin_create_post | Create text, article, or image posts |
| linkedin_delete_post | Delete your posts |
| linkedin_create_comment | Comment on posts |
| linkedin_react_to_post | React to posts (like, celebrate, support, love, insightful, funny) |
| linkedin_upload_image | Upload images for posts |
| linkedin_list_my_posts | List posts created through this server with URNs for reference |
| linkedin_create_event | Create LinkedIn events |
Or add manually to `~/.claude.json`:
```json
{
"mcpServers": {
"linkedin": {
"command": "node",
"args": ["/path/to/linkedin-mcp-server/dist/index.js"],
"env": {
"LINKEDIN_CLIENT_ID": "your_client_id",
"LINKEDIN_CLIENT_SECRET": "your_client_secret"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LINKEDIN_CLIENT_ID | Configuration value read at startup. | Optional |
| LINKEDIN_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| LINKEDIN_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| LINKEDIN_AUTH_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.