Cursor MCP serverfor social media scheduling
Add Posty as a Cursor MCP server and ask the agent to turn the feature you just shipped into a post, schedule it and report back on how it did. 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
- ~/.cursor/mcp.json or .cursor/mcp.json
Connect Cursor in three steps
Posty is a remote MCP server. Cursor adds it by URL, you sign in once in the browser, and every tool call after that runs with your own workspace permissions.
Official Cursor MCP documentation- 1
Add the server
Add this to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json inside one repository. If the file already has other servers, merge the posty entry into the existing mcpServers object.
Cursor setup{ "mcpServers": { "posty": { "url": "https://api.posty.social/mcp" } } } - 2
Sign in and approve access
Open Cursor’s MCP settings, find Posty and connect. 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.
- 3
Choose a workspace and start
Open the agent, make sure the Posty tools are enabled and ask it to list your workspaces. Name the workspace you want in each request. Cursor asks before running a tool by default.
What Cursor 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 Cursor
Replace “Launch” with your workspace name. Each one maps onto the tools above, and Cursor shows you the calls before they run.
Ship it, then say it
Example promptLook at the diff on this branch, draft a LinkedIn post announcing the feature in my Launch workspace and keep it as a draft.Repurpose a doc
Example promptTurn README.md’s Getting started section into a five-slide Instagram carousel caption and save it as a draft in Launch.Tidy the calendar
Example promptList everything scheduled in Launch next week and move anything on Friday to the following Monday at 9am local time.
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 Cursor
- Global or project mcp.json?
- Use ~/.cursor/mcp.json when Posty should be available everywhere you open Cursor. Use .cursor/mcp.json inside a repository when only that project should have it, for example a marketing site whose release notes feed your posts. Both files take the same entry.
- Why does Cursor ask before every tool call?
- That is Cursor’s default for MCP tools, and it is the right default for a tool that can schedule a post. You can inspect the arguments before approving, and Cursor’s run modes let you allow specific tools to run without a prompt. Posty applies your workspace permissions either way.
- Does Cursor support signing in with OAuth?
- Yes. Cursor supports OAuth for remote servers that require it, so Posty needs no header or key in mcp.json. The first connection opens Posty in your browser; Cursor stores the result and refreshes it for you.
- 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 Cursor 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