PluginBench
MCP Server
Active
MIT

LinkedIn MCP Server MCP Server

ai.com.mcp/linkedin

Turn LinkedIn's API into AI-ready MCP tools—retrieve profiles and publish content instantly.

RepositoryRegistry
How to choose

What this kind of tool is for

  • Draft, send, or triage messages and email from inside your agent.
  • Pipe notifications from a build or alert into your team channel automatically.
  • Summarize a busy channel thread into the handful of points that matter.

How to compare servers like this

Channel coverage:
Check the specific app (email, chat, notifications) and whether it reads as well as writes.
Scope of access:
Messages are sensitive; review what the tool can see before connecting an account.
Rate behavior:
Bulk-sending tools should respect provider limits — avoid anything that floods.
Maintenance signal:
APIs in this space change often; recent updates are a strong signal.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the LinkedIn MCP Server MCP server?

The LinkedIn MCP Server exposes LinkedIn's API as Model Context Protocol tools, enabling AI agents to retrieve profile data and publish content. It's built on HAPI MCP, which automatically transforms OpenAPI specifications into MCP-compatible tools without requiring custom code rewrites.

This server bridges LinkedIn's API and AI agents by converting LinkedIn endpoints into MCP tools. Use it to programmatically fetch profile information, retrieve connections, and publish posts—all accessible to Claude, ChatGPT, and other MCP clients. No custom integration logic needed; the server inherits LinkedIn's auth, rate limits, and permissions.

How to install LinkedIn MCP Server

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
~/.cursor/mcp.json
JSON config
{
  "mcpServers": {
    "linkedin": {
      "url": "https://linkedin.run.mcp.com.ai/mcp"
    }
  }
}

Tools & capabilities

Tools this server exposes to the agent.

  • Retrieve Profile Data — Fetch LinkedIn profile information including user details, connections, and profile metadata.
  • Publish Content — Post content to LinkedIn directly from AI agents and workflows.

Use cases

  • Automate LinkedIn profile data retrieval for lead research or CRM enrichment.
  • Generate and publish LinkedIn posts programmatically from AI workflows.
  • Build AI agents that monitor and interact with LinkedIn profiles in real time.
  • Integrate LinkedIn data into multi-tool agent orchestrations via OrcA.
  • Create support or internal assistant bots that pull LinkedIn context on demand.

LinkedIn MCP Server MCP server FAQ

What is the LinkedIn MCP Server?

It's an MCP server that exposes LinkedIn's API as tools for AI agents. Built on HAPI MCP, it automatically converts LinkedIn endpoints into MCP-compatible functions for retrieving profiles and publishing content.

Is it free?

The README does not specify pricing. Check the repository or runMCP documentation for cost details.

How do I install it in Cursor or Claude?

Add the remote MCP endpoint https://linkedin.run.mcp.com.ai/mcp to your MCP client configuration. Cursor and Claude both support remote MCP servers via their settings.

What authentication does it require?

LinkedIn API credentials are required. The server inherits LinkedIn's OAuth 2.0 authentication and permission model; scoped credentials and per-tool permissions flow through automatically.

Do I need to rewrite my LinkedIn integration?

No. HAPI MCP lifts your existing LinkedIn API spec directly into MCP tools. Your auth, validation, and business rules remain unchanged.

Which AI clients can use this server?

Any MCP-compatible client: Claude, ChatGPT, QBot, chatMCP, and custom orchestrators. It's vendor-neutral by design.

README (reference)

Source of truth, from the repository.

HAPI MCP – Headless API for Model Context Protocol

Stop rewriting systems for AI. Instantly turn your APIs into MCP servers.

HAPI MCP lifts your OpenAPI catalog into MCP tools automatically, keeping design (OAS/Arazzo) and runtime (agents/LLMs) cleanly separated. Your existing APIs become AI-ready tools—no new business logic, no sidecar servers, no rework.

Key Features

  • No rewrites: Reuse 100% of your API logic. OpenAPI in, MCP tools out. No parallel codebase or shadow services.
  • Faster time-to-value: Turn specs into agent-ready tools in minutes. Update the spec, ship new tools instantly.
  • Reduced risk: Permissions, auth, rate limits, auditability are inherited from your APIs—governance without bolt-ons.
  • Scales with you: runMCP delivers serverless-like elasticity with long-running when needed. Cold-start fast, stay warm for throughput.
  • Deterministic orchestration: OrcA plans and executes multi-tool tasks predictably—no brittle prompt chaining.
  • Vendor-neutral: Works with any MCP client: ChatGPT, Claude, QBot, chatMCP. OAS + MCP + Arazzo stay portable.

How It Works

  1. Pick your API spec

    • OpenAPI, Swagger, REST—HAPI CLI works with any API specification format.
    • Supports OpenAPI 3.0+, REST APIs, OAuth 2.0 Dynamic Client Registration.
  2. Run a single command

    • One simple CLI command transforms your API into a usable MCP Server.
    • No complex setup, zero configuration, works anywhere, cross-platform.
  3. Use instantly

    • Your API is now ready as a tool, AI agent, or testing interface.
    • MCP server ready, AI agent compatible, testing interface, developer experience friendly.

Visual Pipeline

API Spec (swagger.json) → HAPI CLI → Usable Tool (AI-ready) ← MCP Clients
[ OpenAPI / Swagger ]       [ HAPI CLI ]        [ MCP Server ]
       (Your API)         →   (Transform)   →   (Usable Tool)
                                                 ↑          ↑
                                                 |          |
                                          [ ChatGPT ]  [ runMCP ]
                                          [ Claude  ]  [ OrcA   ]
                                          [ QBot    ]  [ chatMCP]
                                          [ Agents  ]

Who Wins With HAPI

  • Executives: Ship AI initiatives without ballooning cost. Keep teams focused on outcomes, not rewrites and integration sprawl.
  • Architects & PMs: Design with OpenAPI/Arazzo, run with MCP. Clear contracts, policy inheritance, and versioned workflows keep risk low.
  • Engineers & Ops: Deploy once. HAPI Server + runMCP scale tools; QBot/chatMCP give fast feedback; OrcA keeps executions deterministic.

Your Stack, Already Wired

  • HAPI Server: Turns OpenAPI into MCP tools automatically—contracts stay in sync with your source of truth.
  • runMCP: Autoscaling execution and testing for MCP tools; cold-start fast, stay warm when workflows run long.
  • QBot: CLI TUI for power users to interact with MCP tools directly from terminal or scripts.
  • chatMCP: Conversational client that speaks MCP natively for support, ops, and internal assistants.
  • OrcA: Deterministic planning and orchestration for multi-tool tasks; no brittle prompt spaghetti.
  • Agents: Build agentic systems from standard APIs—no custom glue. Connect MCP clients across platforms.

Demos

Documentation

FAQ

  • Do we need to rewrite our services?
    No. HAPI MCP lifts your existing OpenAPI specs directly into MCP tools. Your auth, validation, and business rules remain unchanged.

  • Is this just another MCP server?
    It’s the Headless API model: your API becomes the runtime. HAPI Server reflects it as MCP; runMCP scales it; OrcA orchestrates it. No duplicate logic.

  • Which clients can consume the tools?
    Any MCP client: ChatGPT, Claude, QBot, chatMCP, bespoke orchestrators—vendor-neutral by design.

  • How do we keep control and compliance?
    Your API remains the single source of truth. Policies, RBAC, rate limits, and audit logs flow through automatically; no shadow logic.

  • What about security and privacy?
    Scoped credentials, per-tool permissions, and auditable calls are inherited from your API layer. HAPI adds guardrails and observability for regulated environments.

  • How fast can we get started?
    You can transform your first API into an MCP tool in less than five minutes. The HAPI CLI makes it quick and painless.

Get Started

  1. Install HAPI CLI from latest release: https://github.com/la-rebelion/hapimcp/releases

  2. Transform your OpenAPI spec into an MCP server with a single command:

    hapi serve path/to/your/swagger.json --headless
    
  3. Start using your MCP tools with any compatible client!

  4. Explore the documentation for advanced usage and best practices.

Contributing

Contributions are welcome! Open a discussion or submit a pull request on GitHub: https://github.com/la-rebelion/hapimcp

License

HAPI MCP is licensed under the MIT License. See LICENSE for details.

Related MCP servers

Transform OpenAPI specs into MCP tools instantly—no rewrites, no parallel codebases.

9
HTML
MIT
View repository →

Transform OpenAPI specs into MCP tools instantly—no rewrites, no sidecar servers.

9
HTML
MIT
View repository →

Official MCP Registry: publish and discover MCP servers like an app store for AI agents.

7.3k
Go
View repository →

Search and discover Agent Skills — reusable AI agent capability packages — from the skills.sh registry.

21k
Python
Apache-2.0
View repository →

Turn Strava APIs into AI-ready MCP tools instantly with HAPI—no rewrites, just OpenAPI specs.

9
HTML
MIT
View repository →

One inbox for SMS and email: read threads, search, manage contacts, and send texts and emails.