We-Link MCP Beta
Connect your LinkedIn account directly to AI assistants like Claude, ChatGPT, and Cursor using the We-Link MCP server. Powered by the MCP, this integration lets your AI assistant safely automate tasks through our secure infrastructure. From searching for leads and analyzing profiles to sending messages, you can now manage your LinkedIn workflows entirely through your favorite AI tools.
It enables your AI assistant to perform LinkedIn tasks including:
- Searching profiles
- Reading profile data
- Viewing connections
- Retrieving posts
- Liking posts
- Sending connection requests
- Sending messages
How to get started
Choose your MCP client:
Required Credentials
You need three values before adding the server to your MCP client:
| Credential | Description |
|---|---|
x-api-key | Your We-Link API key from Settings → Security. |
x-api-secret | Your We-Link API secret from the same API key screen. |
account-id | The connected LinkedIn account ID to use for MCP actions. |
For API key setup, see Authentication. To find a connected account ID, see Account Status & Health.
Available Tools
| Action | Description |
|---|---|
| Search profiles | Search LinkedIn profiles using the available filters. |
| Get profile data | Retrieve details for a LinkedIn profile. |
| Send connection request | Send a connection request to a LinkedIn profile. |
| Send message | Send a new message or reply in an existing conversation. |
| Get pending invites | Retrieve pending connection invitations. |
| Get message threads | Retrieve message threads for the connected account. |
| Get messages from threads | Retrieve messages from a selected conversation thread. |
| My connections | Retrieve connections for the connected LinkedIn account. |
| Get posts | Retrieve posts from a LinkedIn profile. |
| Like post | Like a LinkedIn post. |
| Get post reactions | Retrieve reactions to a LinkedIn post. |
Example Prompts
After the server is connected, ask your MCP client for LinkedIn tasks in natural language:
Find me 20 VPs of Sales at SaaS companies in Boston.
Search LinkedIn for Python developers in New York.
Send a connection request to this profile with a short note introducing me.
Limits and Quotas
The MCP server uses native account-level rate limits and rolling daily quotas. These limits protect the connected LinkedIn account from automated behavior flags, security caps, and temporary account restrictions.
If a workflow reaches a daily quota, the server returns QUOTA_EXCEEDED_DAILY message. Wait until the reset time in the error metadata before retrying. For general API limits, see Rate Limits.
Troubleshooting
| Error code | Cause | Fix |
|---|---|---|
WC_AUTH_PIN_REQUIRED | LinkedIn requires OTP, PIN, or phone verification. | Generate the current code and send it in your MCP client when prompted. |
MISSING_WELINK_CREDENTIALS | The MCP client did not send x-api-key or x-api-secret. | Check the MCP configuration and restart or reconnect the client. |
MISSING_ACCOUNT_ID | The MCP client did not send account-id. | Confirm the configured account ID matches a connected We-Link LinkedIn account. |
WC_AUTH_WRONG_PASSWORD | The LinkedIn credentials stored in We-Link are invalid. | Update the credentials in We-Link and retry. |
Handling LinkedIn Verification
When LinkedIn requests verification, follow these steps to authenticate:
-
Get your OTP: Copy the latest OTP from your email or generate it using your LinkedIn 2FA secret in a TOTP-compatible authenticator app.
-
Send the code: Paste and send the code directly into your MCP client chat.
-
Retry workflow: Final step. Once the verification succeeds, retry your original request.
Complete verification promptly. If the auth session expires, restart the verification flow.
Security
Never paste API keys, API secrets, LinkedIn passwords, or LinkedIn session cookies into the AI chat window. Keep them only in the MCP client configuration.