Linkedctl
Drive LinkedIn posts, profile reads, and API workflows from your agent via linkedctl MCP or CLI without bespoke OAuth glue each time.
Overview
linkedctl is a Launch-phase MCP server and CLI that exposes LinkedIn API operations to AI agents through OAuth2-authenticated stdio tools.
What is this MCP server?
- Dual CLI and stdio MCP server for LinkedIn API v0.5.0
- npm linkedctl package invoked with positional argument mcp for agent transport
- OAuth2 via required LINKEDCTL_ACCESS_TOKEN plus optional client ID and secret env vars
- GitHub repository alexey-pelykh/linkedctl for updates and issue tracking
- Fits agent-driven launch posts and profile or network lookups where API access is approved
- Server version 0.5.0
- npm identifier linkedctl with positional package argument mcp
- Three environment variables documented for OAuth (one required secret token)
Community signal: 2 GitHub stars.
What problem does it solve?
Indie hackers stall on launch day because wiring LinkedIn OAuth and repeatable API calls into an agent session takes custom scripts every time.
Who is it for?
Solo founders with LinkedIn API access who want agent-assisted posting, lookups, and CLI parity for launch distribution.
Skip if: Builders without LinkedIn API approval, teams needing multi-channel social suites, or use cases that violate LinkedIn terms.
What do I get? / Deliverables
Once linkedctl MCP is registered with a valid access token, your agent can run approved LinkedIn API actions from the same workflow that drafts your ship post.
- Agent-invokable LinkedIn API operations within MCP sessions
- CLI parity for the same API surface outside the agent
- Repeatable launch-time LinkedIn workflows without one-off HTTP scripts
Recommended MCP Servers
Journey fit
LinkedIn is a primary distribution channel for indie founders at Launch; wiring the official API into the agent reduces friction for announcements and founder-led content. Distribution fits because linkedctl targets outward-facing LinkedIn API actions—sharing updates and managing presence—not in-app product analytics.
How it compares
LinkedIn API MCP and CLI, not an SEO or app-store optimization skill.
Common Questions / FAQ
Who is linkedctl for?
It is for developers and founders who already have LinkedIn API credentials and want MCP or CLI access from coding agents for distribution workflows.
When should I use linkedctl?
Use it at Launch when you are shipping announcements, founder content, or API-backed LinkedIn automation alongside your release checklist.
How do I add linkedctl to my agent?
Install npm package linkedctl, configure stdio MCP with the mcp positional argument, and set LINKEDCTL_ACCESS_TOKEN plus optional OAuth client env vars.