LinkedIn MCP server: let Claude or any agent post to your LinkedIn profile

Set it up and post, step by step

1. Add PostWire's MCP server to your agent

   In Claude, open PostWire in the connector directory and press Connect. Anywhere else, add the remote server https://postwire.io/api/mcp (Streamable HTTP; OAuth sign-in or an API key) — in Claude Code: claude mcp add --transport http postwire https://postwire.io/api/mcp. Cursor, VS Code, Windsurf, Codex and Gemini CLI configs: MCP client configs.

2. Sign in with your email

   The first time the agent uses a PostWire tool, a sign-in window asks for your email and a 6-digit code; that also creates a free PostWire account if you have none. No password and no card. Agents that cannot do OAuth send an API key instead (dashboard → API & MCP → Copy key).

3. Connect your LinkedIn profile

   Ask "connect my LinkedIn". The agent calls create_connect_link and gives you a one-hour link; you sign in on LinkedIn's own page and allow PostWire to post for you (LinkedIn's w_member_social permission). PostWire never sees your password.

4. Let PostWire write the post

   "Write a LinkedIn post about what we learned moving to usage-based pricing, and a Bluesky version." generate_posts returns one draft per network and publishes nothing. LinkedIn's draft is written in the first person with the hook in the first 210 characters — the part the feed shows before "see more" — short lines, an open question to close and 3 hashtags at the end. It keeps links out of the body.

5. Add images or a PDF, if you want them

   Pass public https links in media: 1 to 20 images (each with its own alt text), or one item of type document — a PDF, PowerPoint or Word file that LinkedIn shows as a swipeable carousel, with a title of up to 200 characters. A file on your phone or laptop gets there through create_upload_link: a 24-hour page where you pick the file (up to 250 MB on the free plan and 1 GB on paid plans), then get_uploaded_file returns its media_url.

6. Publish, or schedule it

   After you approve the draft, the agent calls post_to_social (or schedule_post with a run_at time, or "next_slot" for your next free queue slot). A PDF carousel looks like this:

   {
     "name": "post_to_social",
     "arguments": {
       "platforms": ["linkedin"],
       "per_platform": { "linkedin": { "text": "We moved to usage-based pricing in March.\n\nThree things we got wrong …\n\n#pricing #saas #b2b" } },
       "media": [
         { "url": "https://postwire.io/m/…/pricing-lessons.pdf", "type": "document", "title": "3 pricing lessons" }
       ]
     }
   }

7. Open the post

   The result carries the post's link (https://www.linkedin.com/feed/update/…) and the profile it went to. list_scheduled_posts shows what is still queued and cancel_scheduled_post removes one before it goes out.

A link in the first comment instead of the body: the REST API takes "options": {"linkedin": {"first_comment": "Full write-up: https://…"}} on POST /api/post and POST /api/schedule, and a bulk_schedule CSV has a first_comment column. PostWire posts the comment as you, right after the post. See network options.