MCP (streamable HTTP) · LinkedIn

Cline for LinkedIn drafts, with approval built in

Cline is popular with developers who want to choose their own model and see every action before it runs. That makes it a good fit for writing LinkedIn posts about technical work for a wider audience: case studies, lessons from a migration, a hiring post for your team. Cline drafts the post from files in the workspace, you confirm the tool call, and SocialHandoff still holds the post for a final approval in the inbox.

Prompt

Read docs/case-studies/postgres-migration.md. Write a LinkedIn post for CTOs about what we learned moving 2 TB from MySQL to Postgres with no downtime. Three lessons, each in 1 or 2 sentences, and a link to the full write-up at the end. Draft it for LinkedIn.

How to do it

  1. Mint a key Create a Cline key scoped to LinkedIn with the draft permission.
  2. Edit cline_mcp_settings.json From the MCP Servers panel, add a stdio entry for npx -y socialhandoff-mcp with your URL and key, or a remote entry for https://app.socialhandoff.com/mcp.
  3. Confirm the tool call When Cline proposes draft_post, read the body in the approval prompt before allowing it.
  4. Preview Ask Cline to call preview_posts to see how the post renders.
  5. Approve in the inbox The final approval happens in the inbox, not in Cline.

Example draft

We moved 2 TB from MySQL to Postgres without taking the product down. Three things we would tell any CTO planning the same move:

1. Dual writes are the easy part. Proving the two databases match is the project. Budget for the checker.

2. Move reads first, one endpoint at a time, behind a flag. Rolling back a read is free.

3. Your ORM hides more MySQL behavior than you think. Case-insensitive comparisons bit us in 4 places.

The full write-up with our cutover checklist: https://example.com/blog/postgres-migration

Gotchas

  • Numbered lines like 1. and 2. are fine; LinkedIn shows them as typed. Markdown bold or headings are not rendered.
  • Parentheses and brackets are escaped before publish so they do not break the post. You do not need to avoid them.
  • Link previews on LinkedIn come from the linked page. The image attached to the post takes the place of a preview card, and only one image is allowed.
LinkedIn
  • Character limit: 3,000 characters for a post. The feed shows the first few lines and hides the rest behind a see more link.
  • Media per post: LinkedIn allows multi-image posts, documents, and video. SocialHandoff publishes 1 image per post.
  • Alt text: Supported on images through the API's alt text field. Not available for video or documents.
  • Threads: LinkedIn has no threads. If a draft has several parts, SocialHandoff joins them into one post.
A LinkedIn post scheduler that waits for your approval

Frequently asked questions

Does auto-approve in Cline skip the inbox?
No. Cline's auto-approve covers its own tool confirmations. Publishing still needs approval in the inbox unless the key was promoted.
Which Cline models work?
Any model Cline supports. The server stores the text; it does not care which model wrote it.

Let your agents post. Keep the final say.

Connect your first agent in minutes. Every draft waits in your inbox until you approve it.

14 days free. No card required.

The hosted version is opening soon

Leave your email and we will send one message when hosted accounts open, with your 14-day trial ready. Want it today? Self-host it free from the repo.

Start free trial