Claude Code MCP serverfor social media scheduling
Add Posty as a Claude Code MCP server and let Claude draft from your diffs, your docs and your notes, then move posts through review and onto the calendar. Sign in with Posty. Your workspace permissions apply.
https://api.posty.social/mcp- Transport
- Streamable HTTP
- Sign in
- OAuth with your Posty account
- Permissions
- Your workspace role, checked per call
- Plans
- Growth and Accelerate
- Stored in
- ~/.claude.json or .mcp.json
Connect Claude Code in three steps
Posty is a remote MCP server. Claude Code adds it by URL, you sign in once in the browser, and every tool call after that runs with your own workspace permissions.
Official Claude Code MCP documentation- 1
Add the server
Run this in any terminal. The user scope makes Posty available in every project; drop the scope flag to keep it to the current project, or use the project scope to write a .mcp.json your team can commit.
Claude Code setupclaude mcp add --transport http --scope user posty https://api.posty.social/mcp - 2
Sign in and approve access
Start Claude Code, run its MCP command, select Posty and follow the prompts. Posty opens in your browser. Sign in, choose the workspaces this connection may reach and approve access. No API key is created or pasted anywhere. Tokens are stored securely and refreshed for you.
Inside Claude Code/mcp - 3
Choose a workspace and start
Back in Claude Code, ask it to list your Posty workspaces, then name the one you want in each request. Approve tool calls when prompted. The VS Code and JetBrains extensions use the same configuration, so the server is there too.
What Claude Code can do once it’s connected
Every tool mirrors one operation of the public API, so anything a script can do, your assistant can do, within your role. The server publishes its full tool catalog with every schema.
- Posts and scheduling
- Create drafts with text and settings per channel, move them onto the calendar, reschedule up to 50 at once and read delivery history.
create_postupdate_post_contentbulk_schedule_posts - Approvals
- Submit a post for review, approve it or request changes, and see who has been asked and how each ask ended. Approval rules stay in force.
act_on_postlist_post_review_requestsget_post_history - Media
- Upload images and video into the library, organise folders, set alt text and attach files to a post’s channels.
create_media_uploadreplace_post_content_mediaset_media_alt_text - Campaigns
- Create a campaign brief with objective, personas and dates, file posts under it and read its results against the brief.
create_campaignadd_post_to_campaignget_campaign_results - Analytics
- Workspace KPIs against the previous period, per post performance, audience demographics and the metrics each platform reports.
get_analytics_overviewget_analytics_detailget_post_native_metrics - Inbox
- Read comments and direct messages from connected channels, reply, assign a teammate and change a conversation’s status.
list_inbox_conversationslist_post_commentscreate_post_comment
Things to ask Claude Code
Replace “Launch” with your workspace name. Each one maps onto the tools above, and Claude Code shows you the calls before they run.
From a pull request to a post
Example promptSummarise what shipped in the last five merged pull requests and draft a Threads post about it in my Launch workspace. Leave it as a draft.A week of drafts
Example promptIn Launch, draft five short LinkedIn posts from docs/launch-notes.md, one per feature, and put them in the backlog without scheduling.Move a post through review
Example promptSubmit the newest draft in Launch for review and tell me who still has to approve it.
Your workflow.
Still your call.
Posty checks workspace membership and permissions on every call. Drafts, approvals and scheduling follow the same rules as the app, and a token never freezes a permission you have since lost.
You can work across any workspace you have access to. Tell your assistant which one to use, review its drafts, and publish when you’re ready. See the roles and visibility matrix for what each role can do.
Questions about Posty and Claude Code
- Which scope should I use: local, project or user?
- User scope stores the server in your home configuration and loads it in every project, which suits a personal connection. Project scope writes a .mcp.json at the repository root that teammates get from version control; Claude Code asks each person to approve it before use. Local, the default, keeps it to the current project on your machine only.
- How do I sign out or remove the server?
- Choose Clear authentication for Posty in the /mcp menu, or run the Claude Code MCP logout command from your shell. Removing the server with the MCP remove command also deletes its stored tokens and client registration.
- Does the server work in the VS Code and JetBrains extensions?
- Yes. The extensions and the CLI save to the same MCP configuration, and the /mcp dialog in the chat panel manages the same servers, so a server added in the terminal appears in the editor and the other way round.
- Which permissions does the assistant get?
- Exactly yours. Every tool call checks your workspace membership and role at that moment, so an assistant can only see the workspaces you belong to and do what you could do in the app. Approval rules still apply: a workspace that requires review before scheduling requires it from your assistant too.
- Which Posty plans include MCP access?
- The Growth and Accelerate plans, the same plans that include the public API. A workspace on another plan returns a clear plan error instead of connecting.
- Can one connection work across several workspaces?
- Yes. Ask the assistant to list your workspaces first, then name the one you mean in each request. Every tool takes a workspace, so an agency can draft for one client and check analytics for another in the same conversation.
Use Posty from another assistant too
One server, the same sign-in and the same permissions in every client. Each one has its own guide.
Your assistant. Your workspace. Your rules.
Create a workspace, connect Claude Code and keep every post inside the approvals and permissions your team already uses.
MCP access is included on Growth and Accelerate, from $39 per workspace a month. Compare plans