Works with all AI agents

Connect Cursor to social media

Paste one block into mcp.json and Cursor’s agent can write the release post from the code it just changed, then schedule it to all top platforms. The posts land in your PostEverywhere calendar, ready for anyone on the team to check.

$0 due today, cancel anytime

Works with any AI agent
Creator profileBusiness owner profileSocial media manager profileEntrepreneur profileContent creator profile

Used by 2,831 happy customers

Setup in mcp.json

Add the PostEverywhere MCP server to Cursor with mcp.json

Cursor reads its MCP servers from a JSON file. The block below runs the open-source PostEverywhere server through npx with your API key, and Cursor picks up the change without a restart. The whole job is a key, a paste and a quick test.

  1. 1

    Create an API key.

    In PostEverywhere, open Developers in the sidebar and create a key. It begins with pe_live_ and is only shown once. Connect the profiles you want to post to under Accounts first, because Cursor can only reach accounts you have already linked.

  2. 2

    Open the MCP settings.

    In Cursor, open Cursor Settings and go to Tools & MCP, then add a new MCP server. Cursor opens ~/.cursor/mcp.json for you. You can also edit that file directly in any editor.

  3. 3

    Paste the PostEverywhere block.

    Add this under mcpServers, swap in your key and save. If the file already lists other servers, add posteverywhere alongside them inside the same mcpServers object.

    {
      "mcpServers": {
        "posteverywhere": {
          "command": "npx",
          "args": ["-y", "@posteverywhere/mcp"],
          "env": { "POSTEVERYWHERE_API_KEY": "pe_live_YOUR_KEY" }
        }
      }
    }
  4. 4

    Test it in the agent.

    Back in Tools & MCP, PostEverywhere should show as running with its tools listed. Open the agent chat and ask “Show me my connected social accounts on PostEverywhere.” Cursor calls list_accounts and returns your profiles.

What you need to connect Cursor to social media

A recent Cursor build with MCP support (if you cannot find an MCP section, update Cursor and check your Cursor plan includes it), Node.js 18 or newer for npx, and a PostEverywhere account with an API key. API and MCP access are part of every PostEverywhere plan.

What you can ask

Cursor prompts to schedule social media posts from Agent chat

The prompts worth running in an editor are the ones that use what the editor already has open: commits, the README, release notes, screenshots in the repo. Each one below calls real PostEverywhere tools, and Cursor shows the call before it runs unless you have turned on auto-run.

Ask Cursor
  • “Turn the README intro into a five-part series for X (Twitter) and spread it across next week at 9am.”

    Writes five posts and schedules one a day.

  • “Summarise what changed in this PR for a non-technical audience and post it to LinkedIn now.”

    Publishes straight away instead of scheduling.

  • “Show me next week’s queue and tell me where the gaps are.”

    Reads the queue and your scheduled posts, then points out empty days.

  • “Which of my accounts have not had a post in the last fourteen days?”

    Cross-checks accounts against recent posts.

  • “The image for this release is at our docs URL. Import it and attach it to Friday’s Instagram post.”

    Imports media from a public link and updates the post.

  • “Did anything fail to publish this week? Retry whatever failed.”

    Finds failed posts and retries them in one go.

Skills for Cursor

PostEverywhere skills inside Cursor

Run one npx command in your project and the Cursor agent gets the PostEverywhere skills next to the MCP server you configured. The skills are plain markdown, so you can open them in the editor, read exactly what the agent will do, and adjust a rule for your team before anyone posts.

npx

Install for Any agent

For any other agent that reads skills, add them with one npx command.

npx skills add posteverywhere/claude-plugin
See all skills and prompts
  • Repurpose content

    Turn a blog post, transcript or newsletter into a set of posts.

  • Write an X thread or Article

    Write an X thread or long-form X Article and post it.

  • Launch announcement

    Teaser, launch-day, reminder and last-call posts for a launch, event or sale.

  • Brand voice

    Learn how you write from your own posts and keep new posts in your voice.

  • Schedule social posts

    Write, schedule or publish a post to any connected account.

  • Review post performance

    See how posts did and which platform works best.

Prompts to try in Cursor

See all skills and prompts
  • “Use the open file as the source, write three LinkedIn posts from it, and schedule them for Monday, Wednesday and Friday at 9am in PostEverywhere.”

    Skill: Repurpose content
  • “Write an X Article from blog/architecture.md with PostEverywhere and save it as a draft so I can read it before it goes out.”

    Skill: Write an X thread or Article
  • “Read our last 20 LinkedIn posts in PostEverywhere and put a short voice guide in docs/voice.md.”

    Skill: Brand voice

From editor to calendar

Ship a changelog post from Cursor

You merge the feature, the changelog is fresh, and the announcement is the last chore before the weekend. Ask Cursor’s agent to write it from the diff and schedule it, then let your marketing lead review it in the PostEverywhere calendar without opening the repo. Every post Cursor creates appears there with its status, from Draft to Scheduled to Posted.

Context from the repo.
Cursor can read the files and commits you point it at, so the post describes what actually shipped.
Review outside the editor.
Teammates edit wording, swap images or move times in the calendar, with no Cursor seat needed.
Queue openings.
Ask for the next free opening in your posting queue instead of picking a time yourself.
Calendar
MonthWeekDay
Today

Mon

2

  • 9:00 AM

    Week ahead: what is shipping

Tue

3

  • 12:00 PM

    Behind the refactor

Wed

4

  • 3:00 PM

    Open source: our CSV parser

PostedScheduled

Post from Cursor to every top platform from your editor

Link your profiles to PostEverywhere once and Cursor can target any of them in a single request. Each network gets its own format through its official API, so you write one instruction instead of five integrations.

  • Instagram

    Instagram Graph API

  • Facebook

    Meta Graph API

  • X

    X API v2

  • LinkedIn

    LinkedIn Marketing API

  • TikTok

    Content Posting API

  • Threads

    Meta Threads API

  • Bluesky

    AT Protocol

  • Telegram

    Telegram Bot API

  • Discord

    Discord webhooks

  • YouTube

    YouTube Data API v3

  • Pinterest

    Pinterest API

  • WordPress

    WordPress REST API

Cursor limits and troubleshooting for mcp.json

If PostEverywhere does not show up or a call fails, it is almost always one of these.
Analytics
ReachActivityAudienceAccountsDeliveryPosts

By platform

  • Instagram64 sent
  • LinkedIn48 sent
  • X40 sent
  • Facebook31 sent
  • TikTok1 of 22 failed
  • YouTube12 sent

Why posts failed

Grouped by cause, most common first

1

This video is outside the length TikTok allows for this account.

Example data

  • The server shows as failed or has no tools. Usually malformed JSON: a trailing comma, a missing brace, or a second mcpServers object. Check that your Node.js version is 18 or newer (node -v prints it), because npx needs it to start the server.

  • Unauthorized errors. The key is wrong, revoked or wrapped in extra quotes or spaces. Copy it again from the Developers page; it should start with pe_live_.

  • Keep publishing on manual approval. Cursor can run tools without asking once auto-run is on. For a server that can publish to your brand accounts, leave approval on, or switch off individual tools such as delete_post in the MCP settings.

  • Local files are not uploaded. The MCP server imports media from a public URL, not from your disk. Put the image somewhere reachable, such as your docs site or a public bucket, then ask Cursor to import it.

  • Rate limits. Each API key gets 60 requests a minute and 1,000 an hour. For large batches, ask for bulk_create_posts, which takes up to 50 posts per call. Details are in our rate limits guide.

  • Publish now cannot be undone. Scheduled posts can be edited or deleted until they go out. Most networks do not let outside tools recall a published post, so ask Cursor to schedule rather than publish while you get used to it.

Where the config lives

Project config or global config in Cursor

Cursor reads MCP servers from two places. A global config at ~/.cursor/mcp.json follows you into every project, which suits the person who posts for the company whatever they happen to be working on. A project config at .cursor/mcp.json in the repository root only loads when that project is open, which suits a repo tied to one product and one set of brand accounts.
GET /posts/{id}/results
publishing
POST /api/v1/posts
{ "content": "Launch week is here",
  "account_ids": [101, 102, 103, 104, 105],
  "scheduled_for": "2026-10-06T09:00:00Z" }
  • northwind.coffeedone
  • Northwind Coffeedone
  • northwindverifying
  • northwindcoffeeuploading
  • Northwind Coffeeretry_scheduled

One request, one result per accountExample data

  • If you commit a project config so the whole team gets the same tools, keep the key out of it. Cursor can read environment variables in mcp.json, so write the value as ${env:POSTEVERYWHERE_API_KEY} and have each developer set that variable in their own shell. Each person then posts with their own revocable key.

  • The same JSON block works in Windsurf, where it goes in mcp_config.json, and in Cline. Codex uses TOML instead, which the Codex setup guide covers.

  • Prefer the hosted server? Instead of running npx locally, point Cursor at the hosted address: give the posteverywhere entry a "url" of https://mcp.posteverywhere.ai and a "headers" object with "Authorization": "Bearer pe_live_YOUR_KEY". Nothing runs on your machine and you do not need Node.js. Both routes expose the same 38 tools.

  • Not every release needs an agent. If every launch always goes to the same accounts with the same template, a script or CI step calling the social media API is simpler and cheaper. Most teams keep both: Cursor for the posts that need judgement, the API for the ones that do not. Our build a social media agent guide covers the hybrid.

Start 7-day free trial

$0 due today, cancel anytime

Connect another AI agent

Your PostEverywhere key and calendar work with every other assistant and editor too.

Pricing

Simple pricing, unlimited posts on every plan

Every plan posts to all top platforms and includes the API and hosted MCP server for your AI agent.

Lite

$9/mo

  • 2 social accounts
  • 10 AI credits/mo
  • 1 team member
Start 7-day free trial

Starter

$19/mo

  • 5 social accounts
  • 25 AI credits/mo
  • 2 team members
Start 7-day free trial
Most popular

Growth

$29/mo

  • 10 social accounts
  • 100 AI credits/mo
  • 3 team members
Start 7-day free trial

Scale

$39/mo

  • 20 social accounts
  • 500 AI credits/mo
  • 5 team members
Start 7-day free trial

7-day free trial on every plan. Card required, $0 due today, cancel anytime. Compare every plan

FAQ

Cursor social media FAQ

Straight answers about plans, platforms and how scheduling works.

How do I add an MCP server to Cursor?

Open Cursor Settings, go to Tools & MCP and add a new server, which opens mcp.json. Paste the PostEverywhere block with your API key and save. Cursor loads it without a restart.

Can I use MCP with Cursor?

Yes. Cursor’s agent can call tools from any MCP server you add, local or hosted. PostEverywhere’s server gives it tools to schedule, publish, import media, check accounts and read results.

Does Cursor need an API key for PostEverywhere?

Yes. The key goes in the env block of mcp.json, or in an Authorization header if you use the hosted address. Create it on the Developers page and revoke it whenever you like.

Can Cursor schedule posts for later?

Yes. Ask for a date and time and Cursor books it; times are stored in UTC and converted from whatever zone you name. It can also save drafts, put posts into your queue’s next openings and move posts that are already scheduled.

Can I share the PostEverywhere MCP config with my team?

Yes. Commit .cursor/mcp.json to the repo with the key written as an environment variable reference, and each teammate supplies their own key. Never commit a real pe_live_ key.

Can I run Cursor and other MCP clients against the same account?

Yes. Each client keeps its own config and they all point at the same PostEverywhere workspace, so everything lands in one calendar.

Is there a free trial?

Every plan starts with a 7-day free trial. You enter a card at sign-up, owe $0 until the trial ends and can cancel at any point during it. PostEverywhere does not offer a free plan, and every plan includes the API key Cursor uses.

Still have questions?

Contact us or browse the full FAQ.

Start 7-day free trial

$0 due today, cancel anytime

Announce it from the editor you shipped it in

Create a key, paste one block into mcp.json, and ask Cursor for the launch posts.

Start 7-day free trial

$0 due today, cancel anytime

See pricing
Kim V. profile photo
“This tool has truly made my content posting so much easier, I can't work without it. I can schedule my posts days in advance while working on other projects. Set it and forget it.”
Kim V.·Content Creator