How to post on social media from Claude

What you need

You need Claude, either the app or Claude Code in your terminal, and a Content Postiz account with at least one social channel connected. The link between them uses MCP, so there is no code to write and no API key to paste.

Connect your social channels in Content Postiz first. Claude can only work with the channels that are already there.

Custom connectors can depend on your Claude plan and settings, so if you do not see the option, check Claude’s own help pages for what your plan includes.

How the connection works

When you add Content Postiz to Claude, Claude learns the list of things Content Postiz can do: create a post, find free slots, preview a post, attach media, read what is scheduled. You then ask in plain language, and Claude decides which of those to use.

You sign in through Content Postiz’s own login page, so Claude never sees your password. You also pick a workspace, and Claude can only reach that workspace.

Connect Claude in the app

Open Claude’s connector settings and add a custom connector. Paste the Content Postiz URL into the URL field, add it, then choose Connect.

Log in to Content Postiz when the sign-in page opens, then pick the workspace Claude may use. Claude only sees that workspace, which matters if you manage more than one brand.

https://content-postiz.vercel.app/mcp

Connect Claude Code instead

If you work in the terminal, register the server with one command. Then type /mcp inside Claude Code, choose Content Postiz and sign in.

claude mcp add --transport http content-postiz https://content-postiz.vercel.app/mcp

Check that it works

Ask Claude which social channels are connected to your workspace. A correct list means the connection is live. If Claude says it has no such tools, see the troubleshooting section below.

How to write prompts that give better drafts

Claude writes the post you ask for, so give it what it needs. A good prompt for a post has five parts.

• The network and format: “a LinkedIn post”, “an X thread”, “an Instagram carousel caption”.
• The audience: “founders of early-stage software companies”.
• The point: what the post should say, in a sentence.
• The tone and length: “friendly, plain, under 150 words, no hashtags”.
• What to do with it: “draft only”, “schedule for Thursday morning” or “add to the queue”.

Teach Claude your voice once

Describe how you write in one place, so you do not repeat it. In the Claude app you can keep your tone notes in a project or custom instructions, where available on your plan. In Claude Code you can put a short brand-voice note in your project’s CLAUDE.md file.

A useful note says who you write for, words you like and words you avoid, and two or three examples of posts you were happy with.

Ten prompts to try

Start small, so you can see how Claude behaves before you hand it a whole week. Change the details to fit your own accounts.

• “Which social channels are connected to my workspace?”
• “Draft one LinkedIn post about our latest release. Keep it under 150 words and do not schedule it yet.”
• “Turn that into a thread for X, and keep each post under the limit.”
• “Show me what is scheduled for the next seven days.”
• “Move the Thursday post to Friday morning and change the first line to a question.”
• “Find three free slots next week and schedule the LinkedIn post in the best one.”
• “Take these meeting notes and suggest five post ideas for LinkedIn and X. Do not draft yet.”
• “Rewrite this post for Instagram with a friendlier tone and a question at the end.”
• “Attach this image to the post and show me a preview.”
• “Summarise how last week’s posts performed and suggest two things to try this week.”

A walkthrough: from notes to a scheduled week

Here is what a real session can look like. You paste a page of notes from your week and type: “Here are my notes from this week. Pick the two most interesting things for a founder audience and draft a LinkedIn post for each. Do not schedule them.”

Claude replies with two drafts. You read them, and say: “The second one is better. Make it shorter and open with the question.” It rewrites.

When you are happy, you say: “Find two free slots this week and schedule it for the better one. Then draft an X thread from the same idea, but only a draft.” Claude schedules the LinkedIn post and shows the thread.

Finally you open the Content Postiz calendar and read what is scheduled. Everything Claude did is there to review and change. The whole thing takes minutes, and you stayed in charge of what went out.

Workflows that save the most time

• The weekly batch: paste your notes or a changelog, ask for a week of posts across your networks, and review them on the calendar.
• Repurposing: give Claude a long article or doc and ask for a post for each network, shaped to what that network accepts.
• Queue maintenance: ask Claude to find gaps in the week and fill them from your ideas.
• Editing: ask for a different angle on posts already scheduled, without opening each one.
• Reporting: ask how last week’s posts performed and what to try next.
• Releases: in Claude Code, ask it to read your changelog and announce a release on the networks you use.

Images and video

Claude can attach media from a link when it creates a post. Make or find the image or video first, host it somewhere reachable or keep a link ready, and ask Claude to attach it and show a preview.

Check the preview for each network. A square image that works on one network may crop badly on another.

Announce a release from Claude Code

If you build software, Claude Code is a natural place to post from, because it already has your changelog, your commits and your pull requests in front of it.

A simple routine: after you tag a release, ask Claude Code to read the changelog entry, write a short announcement for each network you use, and schedule it for the next morning. Tell it who the audience is, such as users or fellow developers, and what to link to.

Then read the drafts in your Content Postiz calendar. Developers often want a different tone from the one a marketing team would use, so adjust the wording until it sounds like you.

Ask Claude to read the results

Posting is half the job. Once a week, ask Claude how your recent posts performed and which ones did best, and what you could try next. Claude can read the numbers from your workspace and put them in plain words.

Treat its answer as a starting point. Look at the posts it names, and decide for yourself whether the pattern is real before you change your plan. A single good week can look like a trend.

A useful habit is to end the review by asking for two small experiments for next week, such as a different posting time or a different opening line, and to schedule them straight away.

Keep a human in the loop

Everything Claude schedules appears on your Content Postiz calendar, where you can read and change it before it publishes. If you work with a team, turn on approvals and posts wait for a yes.

Read each draft out loud. If it could have come from any company in your field, ask for a rewrite with a detail only you would know.

Be careful when you paste in text written by someone else, such as an email or a web page. Tell Claude what to do with it, and check the result before it goes out.

Troubleshooting

• Claude does not see the tools: remove the connector and add it again, then start a new chat.
• It uses the wrong workspace: disconnect, reconnect and choose the right workspace at the sign-in step.
• A post did not appear: open the calendar and check the day. If approvals are on, the post may be waiting for review.
• A network is missing: connect it in Content Postiz first, then ask again.
• The sign-in page does not open: check that pop-ups are allowed, or try again in a browser you are signed in to.
• A post looks wrong on one network: ask Claude to preview it for that network and adjust the length or format.

Frequently asked questions