Summary
Wraps the LinkedIn API so you can pull profile data and push posts without writing your own MCP server. Built on HAPI MCP, which auto-generates MCP tools from OpenAPI specs, meaning the LinkedIn endpoints you already know are exposed as callable tools for Claude or any MCP client. Runs serverless at linkedin.run.mcp.com.ai over streamable HTTP. Reach for this when you want LinkedIn integration in an agent workflow but don't want to maintain OAuth flows, rate limits, and API versioning yourself. Your existing LinkedIn API permissions and audit logs carry through, and spec updates propagate to tools automatically.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Tools
Public tool metadata for what this MCP can expose to an agent.
4 tools
LINKEDIN_CREATE_LINKED_IN_POSTCreates a new post on LinkedIn for the authenticated user or an organization they manage; ensure the user has necessary permissions if posting for an organization.6 params
Creates a new post on LinkedIn for the authenticated user or an organization they manage; ensure the user has necessary permissions if posting for an organization.
Parameters* required
authorstringThe URN of the LinkedIn member or organization creating the post. Use the GET_USER_INFO action to retrieve the 'author_id' (URN) for the authenticated user. For an organization, the URN will be in the format 'urn:li:organization:{id}'.
commentarystringThe main text content of the post. This field supports plain text and @-mentions (e.g., @[LinkedIn Member](urn:li:person:xxxx)). Maximum length: 3000 characters.
visibilitystringControls who can see the post. 'PUBLIC' makes it visible to everyone, 'CONNECTIONS' to connections only, 'LOGGED_IN' to signed-in LinkedIn members, and 'CONTAINER' for specific group/event posts.one of
PUBLIC · CONNECTIONS · LOGGED_IN · CONTAINERdefault: PUBLICdistributionobjectSpecifies distribution rules for the post, including feed distribution and targeting.
lifecycleStatestringThe state of the post. Use 'PUBLISHED' to post directly, 'DRAFT' to save as a draft, or 'PUBLISH_REQUESTED' if the post requires review before publishing.default: PUBLISHED
isReshareDisabledByAuthorbooleanSet to true to prevent others from resharing this post.default: false
LINKEDIN_DELETE_LINKED_IN_POSTDeletes a specific LinkedIn post (share) by its unique `share_id`, which must correspond to an existing share.1 params
Deletes a specific LinkedIn post (share) by its unique `share_id`, which must correspond to an existing share.
Parameters* required
share_idstringUnique identifier of the LinkedIn share (post) to be deleted.
LINKEDIN_GET_COMPANY_INFORetrieves organizations where the authenticated user has specific roles (ACLs), to determine their management or content posting capabilities for LinkedIn company pages.4 params
Retrieves organizations where the authenticated user has specific roles (ACLs), to determine their management or content posting capabilities for LinkedIn company pages.
Parameters* required
rolestringThe specific role to filter organization ACLs by.one of
ADMINISTRATOR · DIRECT_SPONSORED_CONTENT_POSTERdefault: ADMINISTRATORcountintegerThe number of organization ACLs to return per page.default: 10
startintegerThe starting index for pagination, representing the number of initial ACLs to skip.default: 0
statestringThe approval state of the role to filter by.one of
APPROVED · REQUESTEDdefault: APPROVEDLINKEDIN_GET_MY_INFOFetches the authenticated LinkedIn user's profile, notably including the 'author_id' required for attributing content such as posts or articles.
Fetches the authenticated LinkedIn user's profile, notably including the 'author_id' required for attributing content such as posts or articles.
No parameter schema in public metadata yet.
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
-
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.
-
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.
-
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
- Playlist with demos
- New HAPI MCP YT Channel with demos API-First and MCP
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
-
Install HAPI CLI from latest release: https://github.com/la-rebelion/hapimcp/releases
-
Transform your OpenAPI spec into an MCP server with a single command:
hapi serve path/to/your/swagger.json --headless -
Start using your MCP tools with any compatible client!
-
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.
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
