linkedin-mcp-server

linkedin-mcp-server is a Model Context Protocol (MCP) server that connects an MCP-compatible LLM/agent to LinkedIn APIs for tasks like people search and profile retrieval, using OAuth 2.0 credentials provided via environment variables.

Evaluated Mar 30, 2026 (22d ago)

Repo ↗ API Gateway mcp linkedin oauth2 typescript llm-tools agent-integration data-enrichment

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

README indicates OAuth 2.0, token refresh management, and environment-based secret management. However, it does not document the OAuth scopes, threat model, secure logging behavior, CSRF/PKCE details (if applicable), or provide concrete evidence of rate-limit handling. TLS is assumed for HTTPS requests via Axios, but explicit enforcement is not stated.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You have an MCP-capable environment (e.g., Claude Desktop) and want an agent-friendly interface to LinkedIn data using OAuth credentials you manage yourself.

Avoid When

You need a fully specified REST/SDK contract, strict guarantees on pagination/retry/idempotency, or you cannot securely manage OAuth client secrets.

Use Cases

• AI-assisted talent sourcing (search for people by keywords/location/company/industry)
• Retrieving LinkedIn profile details for enrichment
• Building lead-generation and account intelligence workflows
• Integrating LinkedIn data retrieval into LLM agent toolchains via MCP

Not For

• Unauthenticated use of LinkedIn data
• High-volume automated scraping outside LinkedIn API policy
• Production workloads requiring documented SLAs, comprehensive error semantics, and stable pagination guarantees

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: OAuth 2.0 (LinkedIn API access; token refresh implied by README)

OAuth: Yes Scopes: No

README shows LINKEDIN_CLIENT_ID and LINKEDIN_CLIENT_SECRET via .env and Claude Desktop env configuration; it does not document required scopes or fine-grained permissions.

Pricing

Free tier: No

Requires CC: No

No pricing information provided in README/manifest; likely open-source project relying on LinkedIn API usage policies and your own infrastructure.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ LinkedIn API constraints/terms may limit what the MCP tools can safely do; ensure your use is compliant with LinkedIn policies.
⚠ README provides example tool names/parameters but not a definitive tool schema or edge-case behavior.
⚠ OAuth token management behavior (refresh, expiry handling) is only described at a high level; agent retry behavior is not specified.

Alternatives

Use LinkedIn APIs directly with your own backend (OAuth + official endpoints) and expose a minimal internal API for your agent Wrap LinkedIn API access with a standard REST API you control (with OpenAPI spec) rather than MCP Use other third-party LinkedIn enrichment providers (when compliant with their terms and your requirements)

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for linkedin-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.