Quick Configuration
Choose the setup that matches your environment.
Before You Start
- Confirm you have the account, endpoint, or API key required for LinkedIn.
- Start with minimum scopes and read-only access where possible.
- Keep secrets in environment variables instead of hardcoding them in JSON.
Hosted / Remote
JSON Hosted Config json
{
"linkedin": {
"url": "https://YOUR_LINKEDIN_MCP_ENDPOINT"
}
}Local CLI (npx)
JSON Local Config json
{
"linkedin": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://YOUR_LINKEDIN_MCP_ENDPOINT"],
"env": {
"LINKEDIN_API_KEY": "YOUR_LINKEDIN_API_KEY"
}
}
}Common Pitfalls & Fixes
- ⚠️ Watch out: Rate limiting, authentication tokens, and data extraction accuracy.
- 🔑 Always store API keys in environment variables, never hardcode them in JSON.
- 🛡️ Start with read-only scopes if available to verify connection safely.
Example Prompts
Once connected, try these prompts to test capabilities:
- Search for jobs matching "software engineer" in San Francisco.
- Extract profile details from a given LinkedIn URL.
- Find company information and employee count.
Verification Checklist
- Run 1-2 real prompts to confirm LinkedIn returns usable data.
- Check that error messages are clear enough for troubleshooting.
- Document the required scopes, dependencies, and env vars for future reuse.