Skip to content
Start free trial

Can Cursor schedule social media posts?

Connect Cursor to PostEveryPlatform with MCP and it can draft and schedule posts for your 12 platforms. Its posts wait for your approval by default, it can do only what you allow, and the activity log shows what it did.

Updated

Best for

  • People who want Cursor to prepare posts for a person to review
  • Teams that already use Cursor and want to limit its publishing permissions
  • Owners who want to decide when an assistant-written post may go out

Not for

  • Workflows that require an agent to approve its own posts or connect social accounts.
  • Teams that require every discovery request and permission refusal in the activity log.
  • Workflows needing X replies or Pinterest comments in the inbox today. X replies are not brought in: our posting partner does not import X comments. Pinterest comments are not available.

What you get

  • Keep control of publishing: agent posts wait for owner approval by default. A key with the explicit skip-approval permission can bypass that hold; replies are outside the post-approval flow. Source
  • Give each key only the permissions it needs. Keys are shown once, stored hashed and revocable. Agents cannot connect accounts, change billing or approve their own posts. Source
  • The activity log records routed API operations and executed MCP tool calls, with their status. Some permission refusals and MCP discovery requests are outside that record; it is not a complete audit of everything an assistant does. Source
  • Connect Cursor through the hosted remote MCP server with OAuth. The consent page lets you select a workspace and permissions, including whether posts may skip approval. Source

How it works

  1. Connect Cursor

    Add a posteveryplatform server with url https://posteveryplatform.com/mcp to .cursor/mcp.json.

  2. Set up access

    Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project.

  3. Choose permissions and review posts

    Cursor signs in with OAuth when first used; switch the server from Customize in the sidebar.

What it costs

There is no Free plan. Read the connection guide for the client you use before granting permissions. PostEveryPlatform Solo is $19 a month for 5 accounts and one seat. Team is $29 for 10 accounts and unlimited seats. These are PostEveryPlatform prices; check your client's terms separately. Every workspace holds one account per network; several brands on the same network need separate workspaces on Agency. A 7-day trial requires a card when offered; check Pricing for today's availability before signing up.

See plans and today's trial offer

Questions people ask

Can I connect Cursor for one project only?

Yes. Use .cursor/mcp.json in that project. The MCP guide also describes ~/.cursor/mcp.json for every project. Cursor signs in with OAuth on first use, and you choose the workspace and permissions on the consent page.

Will posts from Cursor wait for me?

Yes, by default. While the workspace approval switch is on, agent-created scheduled posts and requests to post now wait for the owner, unless the key explicitly allows skipping approval. Drafts remain drafts; replies are outside this post-approval flow.

Can my client approve an agent-written post?

No. Clients can review, comment and approve ordinary posts, but only the workspace owner approves posts an agent wrote. Sharing a review link does not give a client that owner permission.

Can I restrict the integration to drafting?

Yes. Select only the scopes the workflow needs. The read permission covers accounts and posts; draft covers drafts and media. Scheduling and posting now need their own permissions. Revoking an API key stops it from working.

Can I schedule two Instagram brands in one workspace?

No. Each workspace holds one account per network. Two brands on Instagram need separate workspaces on Agency, even when the plan has unused account slots. Instagram also requires an image or video for a post.

Will I see everything the assistant did in the activity log?

No. The activity log records routed API operations and executed MCP tool calls with their status. Some early refusals and MCP discovery requests are outside that record. It does not capture the assistant's private conversation or reasoning.

Related guides

Sources and limits

  1. Approval and scoped keys agent-kit/README.md:17
  2. MCP connection guide public/docs-mcp.html:312
  3. Recorded API operations src/index.js:273
  4. Recorded MCP tool calls src/features/mcp.js:645
  5. Inbox coverage src/providers/bundle.js:495
  6. Plans and limits src/plans.js:11
  7. Accounts per network src/features/team.js:393
  8. Agency workspaces src/index.js:743
  9. Owner-only agent approval src/index.js:1492
  10. Team roles and client connections src/features/team.js:1
  11. Instagram media requirement public/app/platforms.js:6

Choose a plan Read the API docs