Your AI can post to LinkedIn. It just needs one line.

A free LinkedIn post scheduler with a native MCP server, so the AI tool you already use — Claude Code, Claude Desktop, Cursor, Gemini CLI and others — can write, schedule and publish your posts for you. There is also a full REST API if you would rather script it yourself.

Yes. No credit card, no trial timer, and nothing held back behind a paid tier. A free account includes 500 posts a month, 2 connected channels, and the complete REST API and MCP server. Paid plans may return once more platforms are live, and anyone who signs up while it is free keeps the free plan.

LinkedIn personal profiles, today. Adapters for X, LinkedIn Pages, Facebook, Instagram, TikTok, YouTube and Pinterest are built and tested but each is still in its platform’s review or verification queue, so we show them as unavailable rather than letting a post fail silently. They switch on for everyone as they are approved.

Use it, if scheduling one post at a time from the LinkedIn composer is all you need. Come here when you want your AI tool to draft and queue posts for you without opening LinkedIn, a real content calendar and queue, drafts that survive, a reusable media library, and an API you can script.

Anything that speaks MCP. We document Claude Code, Claude Desktop, Cursor, VS Code Copilot, Gemini CLI, Codex, Windsurf and Zed, and any other MCP client follows one of two patterns covered in the setup guide. ChatGPT connectors are not supported yet — they require OAuth and this server authenticates with a bearer token.

Yes, through your AI tool or the API. The upload is chunked and resumable, so large files stream up rather than going in one request that hits a size limit. Ask your AI tool to post a file path and it handles the upload for you.

The REST API is for your own code — POST /api/posts from Python, Node, PHP or any HTTP client. The MCP server is for AI tools: it exposes the same capabilities as tools an agent can call in plain language, with no API code to write.

Not yet — outbound webhooks are on the roadmap, not shipped. Today you poll GET /api/posts/{id} for publish status, which returns per-account state and the platform error message when something fails. We would rather tell you this up front than have you find out after integrating.

Upload images and videos once, then attach them to any post by media_id. AI agents can browse the library by tag or type and attach an existing asset instead of re-uploading it every time.

Any language that can make HTTP requests: Python, Node.js, PHP, Ruby, Go, Rust, Java, .NET. Authentication is a bearer token. If it can POST JSON, it works.

We store what you give us to publish it: your posts, your media, and the OAuth tokens for the channels you connect. We do not sell it, and disconnecting a channel revokes our access while keeping your own post history intact.

Anyone who signed up while it was free keeps the free plan. New paid tiers would sit alongside it, not replace it. That is a commitment, not a plan we intend to quietly revise.