A Free LinkedIn Scheduler Your AI Tools Can Post Through
I started building Schedule & Chill in January. I never announced it. Not a post, not a launch, not a single message to anyone who might have wanted it. Nine people found it and signed up anyway, which is the most useful and most embarrassing fact I have about this product.
So here is the launch I should have done seven months ago.
Schedule & Chill is a free LinkedIn scheduler. No credit card, no trial clock, no "free during beta." The part I actually care about is the second half: your AI tools can post through it. Claude Code, Cursor, Claude Desktop, or any MCP client can draft a post and put it on your schedule in one instruction, without you opening LinkedIn.
#What it actually is
Three ways into the same product:
- A web app. Write a post, pick a time, done. Ordinary scheduler, works like you expect.
- A REST API. Full CRUD for posts, media and connected accounts, with token auth.
- An MCP server. 22 tools, 4 resources and 2 prompts that let an AI agent do everything the web app does.
The MCP server is the reason the product exists. Everything else is scaffolding around it.
#Why not LinkedIn's own scheduler?
Fair question, and it is the first one anybody sensible asks. LinkedIn shipped native scheduling and it is free.
The one-sentence answer: LinkedIn's scheduler is a human-only UI, so a human has to click it. There is no way for an agent to reach it. If your writing already happens inside Claude Code or Cursor, the last step still throws you back into a browser tab to copy, paste, set a time, and confirm.
That copy-paste step is small. It is also the step where a posting habit dies, because it happens at the exact moment you have finished the interesting part.
#What posting through an agent looks like
Concretely, once your account is connected, this is a real instruction:
Draft a LinkedIn post about the bug I just fixed in the queue worker, keep it under 900 characters, no hashtags, and schedule it for Tuesday 9am.
Claude writes it, calls schedule_post, and it is on your calendar. If you do not like it, update_post edits it in place. list_posts shows what is queued. cancel_post pulls it.
Connecting is a button now, not a config file. Schedule & Chill supports OAuth 2.1 with PKCE and dynamic client registration, so in Claude you paste the connector URL and click Connect. There is still a plain bearer-token endpoint for clients that want one, and both are staying, because removing the old one would break every setup already running on it.
If you want the longer version of how agents reach social platforms at all, I wrote that up separately in Can AI Agents Post on Social Media? and How to Build a Claude MCP Server.
#What "free" means here, precisely
Free means free. It does not mean a trial that turns into a monthly bill in thirty days.
| Limit | Free account |
|---|---|
| Connected social accounts | 2 |
| Posts per month | 500 |
| Bulk CSV import | 50 rows |
| Schedule templates | 3 |
| Analytics history | 30 days |
| Team seats | 1 |
| Per-file upload | 400 MB |
500 posts a month is roughly 16 a day. If you hit that on LinkedIn you have a different problem than scheduling.
I will be straight about the plan, because "why is this free" deserves a real answer. Billing code exists in the repo and is switched off. It switches back on when 50 people are publishing four or more posts a month, which is a usage number, not a date. Until then there is nothing to charge for, and charging before that would just be a way of avoiding the question of whether the thing is useful. Anyone using it free now is not being set up for a bait-and-switch.
#What it does not do
The honest list, because you will find this out in ten minutes anyway:
- LinkedIn is the offer. YouTube, Bluesky and Mastodon also work today and you can connect them, but LinkedIn is the one I am building around and the one I will stand behind. Adapters for X, Facebook, Instagram, TikTok and Pinterest exist in the codebase and are each stuck behind a named platform approval, so do not plan on them.
- No outbound webhooks. You poll
GET /api/posts/{id}for publish status and the per-account failure reason. Webhooks are on the list, not in the product. - One seat. No team features, no approval workflows.
- 30 days of analytics. Impressions, engagement, top posts, best-time heatmap, and that is the window.
#How it compares
Nothing here is a category of one, and I am not going to pretend otherwise.
| Tool | What it gives you | Where it stops |
|---|---|---|
| LinkedIn native | Free, zero setup, first-party | Human-only UI, no API or MCP for agents |
| Buffer free tier | Free, 3 channels, known brand | No MCP; API access was shut down and is being rebuilt |
| Postiz | Free, open source, has MCP and an API | You host and maintain it yourself |
| Typefully | Developer-friendly, API and MCP | Built around X and threads, not LinkedIn |
| Schedule & Chill | Free, hosted, MCP-native, built around LinkedIn | One seat, no webhooks, young |
If you want multi-platform coverage across thirteen networks and you are embedding this in a product you sell, Ayrshare is the mature option and I have written honestly about what it costs. If you want open source and you enjoy running your own infrastructure, Postiz is genuinely good. If you want a free hosted LinkedIn scheduler your agent can drive, that is the gap I am aiming at.
#The uncomfortable part
Here is the detail that actually stings.
While I was not launching, nine people signed up anyway. No announcement, no Product Hunt, no posts, no ads. They found it through search or a directory listing and made an account. Four of them connected a LinkedIn profile. Three came back and scheduled a second post. One person queued thirty posts into a product nobody had told him about, and his first one published on time this morning.
That is a small number. It is also the number I could have had in February.
The silence was mine, not the market's. Every extra month of building was a month of shipping features for a user I had invented, when a handful of real ones were already there and could have told me which features to skip. I do not know which parts of this product matter yet. Nine people do.
So the request is not really "sign up." It is: try it, and tell me what is missing. That answer changes what I build next, and right now I am still building on guesses.
#Try it
Schedule & Chill is free at schedulenchill.com. Connect a LinkedIn account, point your MCP client at it, and let Claude schedule something.
If it does not work, or the missing platform is the one you needed, tell me. That is more useful to me right now than a signup.
Tagged with:

Zakir Hossen
Founder of Schedule & Chill. Bootstrapped entrepreneur and software engineer.
Related Posts
Can AI Agents Post on Social Media? Yes — Here's Exactly How
AI agents cannot reach X or LinkedIn on their own. They post through a social posting API or an MCP server that holds the OAuth tokens. Here is how both paths work, what they cost, and how to stop an agent publishing something you regret.
How to Build a Claude MCP Server (From Scratch)
An MCP server exposes your tools to Claude without writing a wrapper per agent framework. Here is what one actually is, how to build a working server, the tool-design mistakes that make agents behave badly, and when to just use someone else's.