Creator OS
creator-oscursorlinkedinmcpsocial-media

Cursor MCP LinkedIn Posting: 10-Minute Setup for 2026

Post to LinkedIn from Cursor by adding Creator OS as an MCP server: one config block, OAuth, and you’re publishing from the editor. Setup, scopes, and fixes inside.

Creator OS · October 29, 2026 · 9 min read

Cursor MCP LinkedIn posting means adding a hosted MCP server to Cursor, signing in, and asking the agent to publish a post. Creator OS runs that server at https://mcp.creatoros.ca/mcp. You add it as an mcpServers entry, authorize with a cos_live_ key, and Cursor gets tools like create_post. Setup takes about ten minutes.

Cursor editor
   |
   |  mcp.json: type http + Authorization header
   v
https://mcp.creatoros.ca/mcp
   |
   |  workspace scoped cos_live_ key
   v
Creator OS workspace (your LinkedIn account)
   |
   +--> create_post / update_post  --> LinkedIn feed
   +--> get_post_analytics        --> reads results
   +--> get_best_time_to_post     --> picks the slot
The whole path: one config block, one key, one prompt.

What Cursor MCP LinkedIn Posting Actually Does

You get LinkedIn publishing inside the editor, without writing LinkedIn API code yourself.

Cursor is an MCP client. It reads a config file, connects to the server URL, and lists the tools that server exposes. Creator OS exposes about 160 tools across the account, and the LinkedIn-relevant ones include create_post, update_post, list_posts, get_post, get_post_analytics, get_daily_metrics and get_best_time_to_post. The server handles LinkedIn’s own rules for you, so you pass text, media and a schedule, not a raw Graph payload.

Two things to be clear about up front:

  • The connection is scoped to one workspace. An agency plan gives each client its own workspace, and one workspace’s key cannot post to another.
  • Read-only connections only see read tools, and the API refuses writes from them. That is a deliberate guard, not a bug.

If you would rather see the equivalent walkthrough for another editor, the Windsurf MCP setup guide and the Cursor MCP for social media post cover the same pattern.

Get started for $0

How to Add the LinkedIn MCP Server to Cursor (Step by Step)

The fast path is: sign up, create a key, connect LinkedIn, paste the config block, then test with a read call.

  1. Create a Creator OS account. Start at the sign up page. The free trial starts at $0.
  2. Connect your LinkedIn account. Do this in the web app before you touch Cursor, so the server has something to publish to. Personal profiles and company pages both connect here.
  3. Create an API key. Go to Settings, then API keys. Copy the cos_live_... value. Treat it like a password.
  4. Open Cursor’s MCP settings. Add a new server entry with type http, the server URL, and an Authorization header.
  5. Restart or reload Cursor. The tool list should populate.
  6. Run a read call first. Ask Cursor to list your recent posts. If that works, publishing will too.

The alternative to the header is a browser sign-in: Settings, Connectors, add a custom connector, paste the URL, sign in, pick the workspace, choose read only or read and write. Each connection gets its own key, listed under Settings, Connected apps. That route is friendlier on a shared laptop because you can revoke one connection without touching the others.

Cursor MCP Config File: The Exact mcp.json Block

One entry, three fields, and the key goes in a header, never in a URL.

{
  "mcpServers": {
    "creatoros": {
      "type": "http",
      "url": "https://mcp.creatoros.ca/mcp",
      "headers": {
        "Authorization": "Bearer cos_live_your_key_here"
      }
    }
  }
}

The same shape works in VS Code and Windsurf, since all three read an mcpServers object with a type, a URL and headers. Keep the file out of version control if it holds a live key, or use an environment variable your editor resolves at startup. There is nothing to install and no local process to keep alive, because the server is hosted. That matters on a laptop that sleeps: a local stdio server dies, an HTTP one reconnects.

Field Value Why it matters
type http Hosted server, not a local command
url https://mcp.creatoros.ca/mcp The one endpoint for every plan
headers.Authorization Bearer cos_live_... Identifies the workspace and its permissions

Authorizing the LinkedIn MCP Server: OAuth, Scopes, and Profile vs Company Page

You authorize Creator OS once, and Creator OS holds the LinkedIn connection for you.

That is the part people get wrong. There is no separate LinkedIn OAuth dance inside Cursor, and no scope list to hand-edit in the config file. The OAuth step happens when you connect LinkedIn in the Creator OS web app. After that, the MCP server acts through that stored connection, restricted to the workspace your key belongs to. Scopes and token refresh are Creator OS’s problem, not yours.

Profile versus company page:

  • Personal profile: text, images, video, polls, reposts, a first comment, link preview control.
  • Company page: the same content types, with the organization targeted through organizationUrn, plus audience targeting on page posts once the page has 300 or more members.

One honest limit: LinkedIn carousels published as a PDF document (the swipeable slide format) are not supported through the API yet, so do not plan one through the agent. The LinkedIn MCP server guide and the post options reference list what each content type accepts.

How to Post to LinkedIn From Cursor With a Prompt

A plain English instruction plus the right platform name is enough. The agent picks the tool.

Type this into Cursor’s chat:

Post this to LinkedIn as my company page:
"Shipping our Q1 roadmap today. Three things changed:
pricing, onboarding, and the API. Full notes in the blog."

Add a first comment with the link https://example.com/notes
and schedule it for Tuesday 9am Toronto time.

Behind that prompt, the agent calls create_post with the content, the linkedin platform, the organization target, the first comment, and a schedule_at plus timezone. If you ask it to check length first, it calls check_caption_length. If you ask whether the media is fine, it can call upload_media_from_url and reuse the returned med_ id on more than one platform later.

Two prompts worth keeping around:

What were my best three LinkedIn posts by engagement
in the last 30 days, and what did they have in common?

When is my LinkedIn audience most active this week?
Then move Thursday's draft to that slot.

The second prompt chains get_post_analytics, get_best_time_to_post and update_post. That is the difference between a scheduler and an agent: the agent reads the numbers and edits the plan in the same turn. For a video version of this loop, watch the walkthroughs on the KevBuildsApps YouTube channel.

Can You Schedule LinkedIn Posts From Cursor?

Yes, scheduling is a field on the create call, not a separate product.

You pass a schedule time and a timezone and Creator OS queues it. Ask for a draft instead and it stays a draft until you approve. Some practical habits:

  • Ask Cursor what is already queued before adding more, so you do not stack three posts on one morning. list_posts with a scheduled status filter answers that.
  • Let get_best_time_to_post pick the slot for evergreen posts, and override it by hand for announcements tied to a real event.
  • Keep the prompt specific about timezone. “Tuesday 9am” means nothing without one.

The MCP docs show the full parameter set for scheduling, drafts and per-platform options.

LinkedIn MCP for Claude vs Cursor: What Changes

The server is identical. Only the client’s setup and approval behaviour differ.

Claude Cursor
Where you add it Settings, Connectors, custom connector MCP settings, mcpServers entry
Auth input Browser sign-in, then pick workspace Bearer cos_live_... header
Tools available Same hosted tool set Same hosted tool set
Best fit Writing and planning away from code Shipping copy next to the code that made it

The workflow I would actually recommend is split. Draft and critique the copy in Claude, publish it from Cursor where the changelog lives. Both connections point at the same workspace, so a post drafted in one is visible in the other. The Claude Sonnet MCP guide walks through that side, and Claude Code users have a plugin route with a publish guard that asks Proceed or Cancel before anything goes out.

Common Cursor MCP LinkedIn Errors and Fixes

Nearly every failure is a config, key or permissions problem, and each has a clear symptom.

Symptom Likely cause Fix
No tools appear Server entry missing or malformed Check JSON validity, then reload Cursor
401 or auth failure Key missing, expired or padded wrong Regenerate in Settings, API keys
Read tools work, writes refused Connection is read only Create a read and write connection
Wrong account or page Key belongs to another workspace Use the key for that workspace
Agent keeps asking to confirm Destructive tool guard Expected: approve or cancel
Post fails on one network That platform is not connected Response lists missing_platforms

Two details that save time. First, the write refusal is silent by design: the tool simply is not offered, or the API returns an error. Second, destructive tools such as delete post or disconnect account are marked so the AI app asks before acting. If you see a confirmation prompt, the setup is working.

If you are wiring this up inside Claude Code with the plugin, the Claude Code MCP setup walkthrough covers the config step by step.

FAQ

Is there an official LinkedIn MCP server?

Creator OS is not LinkedIn, and it does not publish an official LinkedIn server. It ships a hosted MCP server of its own at https://mcp.creatoros.ca/mcp that covers LinkedIn publishing, comments and analytics alongside the other platforms on your account. You point Cursor or any MCP-capable client at that URL.

How do I add an MCP server to Cursor?

Open Cursor’s MCP settings and add an entry under mcpServers with "type": "http", the server URL, and an Authorization header carrying your cos_live_ key. Save, reload Cursor, and confirm the tool list populates before you ask it to post. The config block above is the exact shape.

Can I post to LinkedIn from Cursor without the LinkedIn API?

You do not write any LinkedIn API calls, but the posting still goes through LinkedIn’s API. Creator OS holds the LinkedIn connection and applies the platform’s rules, so your prompt just supplies content, media, timing and the target organization. You never manage tokens or scopes in the editor.

Does the LinkedIn MCP server work with company pages?

Yes. Connect the page, then target it through organizationUrn in the post call, or name the page in your prompt. Page posts also support audience targeting once the page has 300 or more members.

What is the difference between LinkedIn MCP and LinkedIn ads MCP?

Posting tools run on every plan and cover organic content, comments and analytics. Paid LinkedIn ads sit behind the Ads add-on at $19.99/month, and cover sponsored posts from a Company Page with a 10/day minimum budget and a LinkedIn review on every ad. The ads docs list the objectives and the linkedin-campaign-builder skill builds the campaign.

Get Started With Creator OS MCP

Start at https://www.creatoros.ca/sign-up, connect LinkedIn, create a key, and paste the config block. Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. The free trial starts at $0 and you can cancel anytime.

If you want the full parameter list before you build, read the docs at https://www.creatoros.ca/docs and the launch video at the Creator OS launch walkthrough.

Get started for $0
Free trial for new subscribers. Cancel anytime.

Keep reading