LinkedIn MCP Server (via HAPI)

MCP server providing LinkedIn API tools — enabling AI agents to retrieve LinkedIn profile data and publish content. Built via the HAPI MCP framework. Enables professional networking agents to read profiles, post updates, and interact with LinkedIn's professional data platform.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Other linkedin social professional-network profile content mcp-server b2b
⚙ Agent Friendliness
64
/ 100
Can an agent use this?
🔒 Security
80
/ 100
Is it safe for agents?
⚡ Reliability
65
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
62
Documentation
60
Error Messages
60
Auth Simplicity
68
Rate Limits
72

🔒 Security

TLS Enforcement
92
Auth Strength
82
Scope Granularity
75
Dep. Hygiene
65
Secret Handling
80

Professional PII data. LinkedIn ToS violations risk bans. OAuth required. GDPR for EU. Strict rate limits limit agent utility. Partner access required for most features.

⚡ Reliability

Uptime/SLA
72
Version Stability
65
Breaking Changes
62
Error Recovery
62
AF Security Reliability

Best When

A sales, recruiting, or marketing professional wants AI agents to assist with LinkedIn activities — retrieving profiles, drafting content, or researching prospects — within LinkedIn's API terms.

Avoid When

Automated outreach or scraping at scale. LinkedIn aggressively enforces its Terms of Service and has strict API access policies. Most LinkedIn API capabilities require partner-level access.

Use Cases

  • Retrieving LinkedIn profiles and professional data from recruiting or sales agents
  • Publishing content and updates to LinkedIn from marketing automation agents
  • Building professional networking workflows with AI-assisted outreach
  • Researching company and professional data for competitive intelligence agents

Not For

  • Mass scraping or bulk profile harvesting (violates LinkedIn Terms of Service)
  • Automated connection requests without user consent
  • Non-professional social platforms (LinkedIn-specific)

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: oauth
OAuth: Yes Scopes: Yes

LinkedIn OAuth 2.0. Most LinkedIn API capabilities require LinkedIn Partner Program access. Basic profile read and post create available with standard OAuth.

Pricing

Model: free
Free tier: Yes
Requires CC: No

MCP server free open source. LinkedIn API access requires app approval. Many features gated behind LinkedIn Partnership tier.

Agent Metadata

Pagination
cursor
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • PRIVACY: LinkedIn profile data is personal professional information — handle with care
  • LinkedIn TOS strictly limits automated scraping and mass outreach — violations lead to account bans
  • Most useful LinkedIn APIs require partner-level access not available to standard developers
  • Rate limits are very restrictive (100 calls/day basic) — multi-user agents will exhaust quickly
  • HAPI framework implementation — validate against current LinkedIn API version

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for LinkedIn MCP Server (via HAPI).

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

$3

Score Monitoring

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

Continuous monitoring

$3/mo

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

6470
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered