|
1 | 1 | Linked API MCP server connects your LinkedIn account to AI assistants like Claude, Cursor, and VS Code. Ask them to search for leads, send messages, analyze profiles, and much more – they'll handle it through our cloud browser, safely and automatically. |
2 | 2 |
|
3 | | -# Use cases |
| 3 | +## Use cases |
4 | 4 | - **Sales automation assistant**. Ask your AI to find leads, check their profiles, and draft personalized outreach. It can search for "software engineers at companies with 50-200 employees in San Francisco", analyze their backgrounds, and suggest connection messages that actually make sense. |
5 | 5 | - **Recruitment assistant**. Let your assistant search for candidates with specific skills, review their experience, and send initial outreach. It handles the time-consuming parts while you focus on actually talking to people. |
6 | 6 | - **Conversation assistant**. Your AI can read your existing LinkedIn conversations and help you respond naturally. It understands the context of your chats, suggests relevant replies, and can even send follow-up messages. |
7 | 7 | - **Market research assistant**. Need competitor analysis? Your assistant can gather data about companies, their employees, and recent activities. Get insights about industry trends without spending hours on LinkedIn. |
8 | 8 |
|
9 | | -# Installation |
10 | | -The MCP server needs tokens to access your LinkedIn account. Here's how to get them: |
| 9 | +## Get started |
| 10 | +To start using Linked API MCP, spend 2 minutes reading these essential guides: |
11 | 11 |
|
12 | | -1. Sign up at [Linked API Platform](https://app.linkedapi.io/?ref=github-mcp). |
13 | | -2. Choose your plan and complete the purchase. |
14 | | -3. Connect your LinkedIn account (it takes about 2 minutes). |
15 | | -4. Copy your tokens from the dashboard: |
16 | | - - `LINKED_API_TOKEN` – your main token that enables Linked API access. |
17 | | - - `IDENTIFICATION_TOKEN` – unique token for your LinkedIn account. |
18 | | - |
19 | | -**Multiple LinkedIn accounts:** |
20 | | - |
21 | | -If you have multiple LinkedIn accounts, you'll get a separate identification token for each one, and you can create multiple MCP server instances – one for each account. |
22 | | - |
23 | | -**Handling long-running workflows:** |
24 | | - |
25 | | -The configuration examples below include a `HEALTH_CHECK_PERIOD` variable. Different applications (Claude, VS Code, Cursor, Windsurf) have different timeout limits for MCP tool calls. Since some LinkedIn workflows can take several minutes to complete, this setting helps the MCP server handle these longer operations correctly – preventing disconnections and ensuring your workflows run to completion. |
26 | | - |
27 | | -## Claude |
28 | | - |
29 | | -Add this to your Claude Desktop configuration file: |
30 | | - |
31 | | -- Mac: `~/Library/Application Support/Claude/claude_desktop_config.json` |
32 | | -- Windows: `%APPDATA%\Claude\claude_desktop_config.json` |
33 | | - |
34 | | -```json |
35 | | -{ |
36 | | - "mcpServers": { |
37 | | - "linkedapi": { |
38 | | - "command": "npx", |
39 | | - "args": ["-y", "linkedapi-mcp@latest"], |
40 | | - "env": { |
41 | | - "LINKED_API_TOKEN": "your-linked-api-token-here", |
42 | | - "IDENTIFICATION_TOKEN": "your-identification-token-here", |
43 | | - "HEALTH_CHECK_PERIOD": "180" |
44 | | - } |
45 | | - } |
46 | | - } |
47 | | -} |
48 | | -``` |
49 | | -Restart Claude Desktop after saving the config. |
50 | | - |
51 | | -## Cursor |
52 | | -Add this configuration to your Cursor settings: |
53 | | -```json |
54 | | -{ |
55 | | - "mcpServers": { |
56 | | - "linkedapi": { |
57 | | - "command": "npx", |
58 | | - "args": ["-y", "linkedapi-mcp@latest"], |
59 | | - "env": { |
60 | | - "LINKED_API_TOKEN": "your-linked-api-token-here", |
61 | | - "IDENTIFICATION_TOKEN": "your-identification-token-here", |
62 | | - "HEALTH_CHECK_PERIOD": "600" |
63 | | - } |
64 | | - } |
65 | | - } |
66 | | -} |
67 | | -``` |
68 | | -You can also configure it through the UI: go to Cursor Settings > Tools & Integrations > MCP Tools Section, then click "New MCP Server" and paste the configuration. |
69 | | - |
70 | | -## VS Code |
71 | | -Install the MCP extension, then add this to your settings: |
72 | | -```json |
73 | | -{ |
74 | | - "mcpServers": { |
75 | | - "linkedapi": { |
76 | | - "command": "npx", |
77 | | - "args": ["-y", "linkedapi-mcp@latest"], |
78 | | - "env": { |
79 | | - "LINKED_API_TOKEN": "your-linked-api-token-here", |
80 | | - "IDENTIFICATION_TOKEN": "your-identification-token-here", |
81 | | - "HEALTH_CHECK_PERIOD": "600" |
82 | | - } |
83 | | - } |
84 | | - } |
85 | | -} |
86 | | -``` |
87 | | - |
88 | | -## Windsurf |
89 | | -Add this to your Windsurf configuration file at `~/.codeium/windsurf/mcp_config.json`: |
90 | | - |
91 | | -```json |
92 | | -{ |
93 | | - "mcpServers": { |
94 | | - "linkedapi": { |
95 | | - "command": "npx", |
96 | | - "args": ["-y", "linkedapi-mcp@latest"], |
97 | | - "env": { |
98 | | - "LINKED_API_TOKEN": "your-linked-api-token-here", |
99 | | - "IDENTIFICATION_TOKEN": "your-identification-token-here", |
100 | | - "HEALTH_CHECK_PERIOD": "600" |
101 | | - } |
102 | | - } |
103 | | - } |
104 | | -} |
105 | | -``` |
106 | | -You can also configure it through the UI: go to Windsurf Settings > Advanced Settings > Cascade section, then click "Add Server" and paste the configuration. |
107 | | - |
108 | | -# Available tools |
109 | | -The MCP server provides these tools for interacting with LinkedIn: |
110 | | - |
111 | | -## Standard interface |
112 | | -| **Tool** | **Description** | |
113 | | -|:---------|----------:| |
114 | | -| `fetch_person` | Get person page information with optional experience, education, skills, posts | |
115 | | -| `fetch_company` | Get company information with optional employees, decision makers, posts | |
116 | | -| `fetch_post` | Get post information and engagement metrics | |
117 | | -| `search_people` | Search for people with advanced filtering | |
118 | | -| `search_companies` | Search for companies with advanced filtering | |
119 | | -| `send_message` | Send message to person | |
120 | | -| `sync_conversation` | Sync conversation for polling | |
121 | | -| `send_connection_request` | Send connection request with optional note | |
122 | | -| `check_connection_status` | Check connection status with person | |
123 | | -| `withdraw_connection_request` | Withdraw pending connection request | |
124 | | -| `retrieve_pending_requests` | Get all pending connection requests | |
125 | | -| `retrieve_connections` | Get your connections with filtering | |
126 | | -| `remove_connection` | Remove person from connections | |
127 | | -| `react_to_post` | React to post (like, love, support, celebrate, insightful, funny) | |
128 | | -| `comment_on_post` | Leave comment on post | |
129 | | -| `retrieve_performance` | Get LinkedIn dashboard analytics | |
130 | | -| `get_api_usage_stats` | Get Linked API usage statistics | |
131 | | - |
132 | | -## Sales Navigator |
133 | | -| **Tool** | **Description** | |
134 | | -|:---------|----------:| |
135 | | -| `nv_fetch_person` | Get person page information from Sales Navigator | |
136 | | -| `nv_fetch_company` | Get company information with optional employees and decision makers from Sales Navigator | |
137 | | -| `nv_search_people` | Search for people with advanced filtering via Sales Navigator | |
138 | | -| `nv_search_companies` | Search for companies with advanced filtering via Sales Navigator | |
139 | | -| `nv_send_message` | Send message to person via Sales Navigator | |
140 | | -| `nv_sync_conversation` | Sync Sales Navigator conversation for polling | |
141 | | - |
142 | | -## Other tools |
143 | | -| **Tool** | **Description** | |
144 | | -|:---------|----------:| |
145 | | -| `poll_conversations` | Monitor Standard and Sales Navigator conversations for new messages | |
146 | | -| `execute_custom_workflow` | Execute custom workflow definition | |
147 | | -| `get_workflow_result` | Get workflow result by ID | |
148 | | - |
149 | | -# Usage examples |
150 | | -With Linked API MCP, you can ask your AI-assistant things like: |
151 | | -> [!TIP] |
152 | | -> Find all decision makers at Acme Corp and send them connection requests. |
153 | | -
|
154 | | -> [!TIP] |
155 | | -> Search for product managers at fintech companies in New York with 50-200 employees. |
156 | | -
|
157 | | -> [!TIP] |
158 | | -> Tell me about 'https[]()://linkedin.com/in/jane-doe' including their work history and experience. |
159 | | -
|
160 | | -> [!TIP] |
161 | | -> Send a connection request to 'https[]()://linkedin.com/in/jane-doe' mentioning their recent article about AI in healthcare. |
162 | | -
|
163 | | -> [!TIP] |
164 | | -> Get all my pending connection requests and withdraw each one of them. |
165 | | -
|
166 | | -These are just basic examples. Since your assistant can execute custom workflows combining multiple actions, the automation potential is truly limitless. |
| 12 | +1. [Installation](https://linkedapi.io/mcp/installation/) – set up MCP in Claude, Cursor, VS Code, or Windsurf. |
| 13 | +2. [Available tools](https://linkedapi.io/mcp/available-tools/) – explore all the LinkedIn tools your assistant can call. |
| 14 | +3. [Usage examples](https://linkedapi.io/mcp/usage-examples/) – see real-world examples to get you started quickly. |
167 | 15 |
|
| 16 | +## License |
| 17 | +This project is licensed under the MIT – see the [LICENSE](https://github.com/Linked-API/linkedapi-mcp/blob/main/LICENSE) file for details. |
0 commit comments