Run Your LinkedIn From Claude, Not a Dashboard
If you already spend half your day in Claude, a separate LinkedIn dashboard is one more tab to remember. You draft a post in Claude, copy it into a scheduler, check analytics somewhere else, and lose the thread of what you were thinking. The natural next question: can I just post to LinkedIn from Claude?
You can, but not out of the box. Claude has no built-in LinkedIn connection, so you add one through a connector. This guide covers the ways to do that, how to set one up in Claude, a week of prompts that run your LinkedIn from the chat, and the guardrails to put in place before Claude touches anything public. For the background on the technology itself, see what a LinkedIn MCP server is.
Quick answer: Claude can't post to LinkedIn by itself. To run LinkedIn from Claude, add a LinkedIn-capable MCP server as a custom connector in Claude's settings, sign in through OAuth, and turn the connector on in your chat. Then you can ask Claude to find post ideas, draft in your voice, schedule approved posts, and check results. Choose a connector that publishes through an official connection, and set it so Claude needs your approval before anything goes live.
Why run LinkedIn from Claude instead of a dashboard?
The best reason to run LinkedIn from Claude is that your thinking already happens there. You work through a pricing decision, a hiring plan, or a customer problem in a chat, and the post is sitting in that conversation. A dashboard asks you to leave, re-explain, and come back.
- Context stays in one place: Claude can see the conversation you just had and, through other connectors, the docs and threads behind it.
- Fewer tools to check: Drafting, scheduling, and results live in one chat instead of three tabs.
- Natural language replaces menus: "Move Thursday's post to next week and draft something on the hiring news instead" is one sentence, not six clicks.
- It fits how agents work: Claude can chain steps such as finding an idea, drafting, scoring, and scheduling in one request. (See AI writer vs AI agent.)
A dashboard still wins in two cases: when you want to see a month of posts on a calendar at a glance, and when several people need to approve posts in a shared view. Most teams end up using both, with Claude for the work and the dashboard for the overview.
What are the Claude LinkedIn integration options?
There's no first-party Claude LinkedIn integration today, so every option is either manual or a third-party connector built on the Model Context Protocol. They differ most in setup effort, account risk and what Claude can do once connected.
| Option | Setup effort | Account risk | What Claude can do |
|---|---|---|---|
| Copy and paste | None | None | Draft only; you post by hand |
| Automation platform (e.g. Zapier, n8n) | Medium | Low to medium | Send a finished post to a fixed workflow |
| Self-hosted open-source MCP server | High, needs code | High if it uses your login or cookies | Varies; often browser automation |
| Hosted connector from a LinkedIn tool | Low, no code | Low with official connections | Ideas, voice, drafts, scheduling and results |
The rest of this guide assumes a hosted connector. It needs no code, carries little account risk, and gives Claude the most to work with: not just a publish button, but ideas, voice and results.
How do you connect a LinkedIn tool to Claude?
Custom connectors that use remote MCP are available on Claude's Free, Pro, Max, Team, and Enterprise plans, but Free users are limited to one custom connector, according to Anthropic's guide to getting started with custom connectors. The steps for Pro and Max:
- Get the server URL: Your LinkedIn tool's settings or docs will give you its remote MCP endpoint.
- Open Claude's connector settings: Go to Customize, then Connectors, choose "+ Add" and then "Add custom connector".
- Name it and paste the URL: Give the connector a clear name and enter the server URL.
- Sign in: Complete the OAuth sign-in to your LinkedIn tool and review the permissions it asks for.
- Turn it on in a chat: In a conversation, open the "+" menu (or type "/"), go to Connectors, and switch your LinkedIn tool on.
On Team and Enterprise plans, an owner adds the connector first under Organization settings, then each member connects their own account. Menu names change over time, so check Anthropic's connector help page if yours looks different.
Before you connect anything
Anthropic advises connecting only to servers built by organizations you trust and reviewing the permissions requested during sign-in. If your LinkedIn tool also asks for access to Slack or Notion, connect those inside the tool rather than giving Claude more connectors than it needs.
What prompts run a week of LinkedIn in Claude?
Once your connector is on, a week can run entirely from the chat. These prompts assume a connector that can list ideas, draft, score, schedule, and report, which is what a content-workflow MCP server offers. Adjust the wording to the tool names your connector shows.
| Day | Job | Prompt |
|---|---|---|
| Monday | Find ideas | "Show me this week's top post ideas from my work, with an engagement estimate for each." |
| Tuesday | Draft | "Draft the second idea in my voice. Leave out customer names and any revenue numbers." |
| Wednesday | Score and edit | "Score this draft for hook and voice, then give me a tighter version of the opening." |
| Thursday | Approve and schedule | "Show me the exact final text. If I say approve, schedule it for the best time this week." |
| Friday | Review results | "How did this week's posts perform, and what should next week's ideas lean toward?" |
Two habits make this work. Say "approve" explicitly, so there's never doubt about which draft is cleared to go. And tell Claude what to leave out every time a draft comes from sensitive material.
This is what an MCP Claude LinkedIn setup is good for: not faster posting, but a shorter path from what you're working on to something worth posting. (See why your work is the best source of LinkedIn content.)
What guardrails should you set before Claude touches LinkedIn?
A connector that can publish is a connector that can publish the wrong thing. Set these up first:
- Make publishing need approval: On Team and Enterprise plans, owners can set each connector tool to "Always allow", "Needs approval" or "Blocked". Set any publish or schedule tool to "Needs approval". On any plan, prefer a connector whose own workflow requires approval before a post goes live.
- Use an echo-back confirmation: Before Claude schedules a post, ask it to show you the exact final text and wait for "approve". Approving a summary isn't the same as approving the post.
- Watch for prompt injection: Anthropic warns that malicious servers or content can try prompt injection. Don't let Claude publish in the same chat where it's reading untrusted web pages or files, and turn off write tools when you're using Claude for research.
- Give the least access that works: Connect only the LinkedIn tool, review the permissions at sign-in, and skip any connector that asks for your LinkedIn password or session cookies.
- Know how to revoke: Find where to disconnect the connector in Claude and where to revoke its token in the LinkedIn tool before you need to.
- Keep accounts separate: Agencies and teams should connect each person's account separately, so one chat never posts as the wrong person.
With these in place, Claude does the work, and you keep the one decision that matters.
How do you run Resonate from Claude?
Resonate is an AI LinkedIn ghostwriter powered by your real work and calibrated to your voice. With Resonate's MCP connector for Claude, the prompts above map straight onto its workflow, so Claude becomes the place you run LinkedIn and Resonate supplies the ideas, the voice and the guardrails.
How the connection is secured. You add Resonate's MCP endpoint in Claude, complete OAuth, and approve which Resonate actions Claude may use. Tokens are scoped, revocable from Resonate's settings, and isolated per workspace. Claude Desktop is officially supported, alongside Cursor and n8n, and MCP is included from Resonate's Starter plan.
Run your LinkedIn from Claude this week. Start a free 14-day Resonate trial and add the connector, or see which Resonate plan includes MCP. Learn more about the AI LinkedIn content generator.
How does running LinkedIn from Claude work for each role?
- Founders and CEOs: You already use Claude as a thinking partner. Turning those conversations into approved posts, without leaving the chat, keeps your LinkedIn consistent through the weeks when you'd never open a dashboard. (See the AI ghostwriter built for busy founders.)
- CMOs, growth, and content marketers: Claude becomes the control room for executive content. You can run the weekly prompt sequence for several leaders, each with their own voice, and keep approvals with each executive.
- Executive assistants and chiefs of staff: You can queue, reschedule, and report on the founder's posts from Claude in plain language. Keep the founder's approval as the one step you never do on their behalf. If you'd rather hand the whole thing off, Resonate also offers a human-edited done-for-you service.
- Agencies and ghostwriters: Use one connection per client workspace, so Claude never mixes voices or posts as the wrong person. Resonate's MCP tokens are isolated per workspace for this reason. See the Resonate plan built for agencies.
- Investors and VC platform teams: A shared Claude-based playbook, with a safe connector and founder approval built in, gives portfolio founders a low-effort way to stay visible. Firms introducing Resonate across a portfolio can apply to the Resonate partner program.
Final takeaway
You don't need another dashboard to stay consistent on LinkedIn. You need Claude, a connector you trust, and one rule: Claude does the finding, drafting, checking, and scheduling, and you approve what goes out. Set that up once and you can post to LinkedIn from Claude without leaving the conversation where your best ideas already start.
Frequently asked questions
Can Claude post to LinkedIn?
Not on its own. Claude has no built-in LinkedIn connection. To post from Claude, you add a third-party LinkedIn connector built on MCP, sign in, and turn it on in your chat.
Is there an official Claude LinkedIn integration?
There's no first-party LinkedIn connector from Anthropic or LinkedIn. Every option today is a third-party MCP server, either hosted by a LinkedIn tool or self-hosted.
Do I need a paid Claude plan to connect LinkedIn?
No. Custom connectors are available on Free, Pro, Max, Team and Enterprise plans, but Free users can add only one custom connector.
Can I make Claude ask before it posts?
Yes. On Team and Enterprise plans, owners can set connector tools to need approval. On any plan, choose a LinkedIn connector that requires your approval in its own workflow, and ask Claude to show the exact text before scheduling.
Is it safe to connect LinkedIn to Claude?
It's safe when the connector publishes through an official connection, uses revocable OAuth tokens and doesn't need your LinkedIn password or cookies. Anthropic also recommends connecting only to servers from organizations you trust.
Can I run LinkedIn from ChatGPT or Cursor too?
Yes, if your LinkedIn tool's MCP server supports them. Resonate's MCP works with Claude Desktop, Cursor and n8n, and with ChatGPT and Zapier through their own MCP clients.
Content Writer @ Resonate
Charlotte explores LinkedIn content, personal branding, AI writing, and founder-led marketing at Resonate. She believes the best content comes from real experience, not generic advice, and writes practical insights to help founders turn what they already know into content that people want to read.
Write LinkedIn content that sounds like you
with Resonate's AI Voice Engine