# How to Connect PostEverywhere to Cursor
> Cursor cannot post to social media on its own. Connect PostEverywhere as an MCP server and your editor can schedule, publish and report across every platform without leaving the command palette. Setup takes about two minutes.
**Source:** https://posteverywhere.ai/blog/connect-cursor-to-social-media
**Author:** Jamie Partridge
**Published:** 2026-09-21
---
You ship a feature on Friday afternoon. The changelog is written, the PR is merged, and now comes the boring part: leaving the editor, opening a scheduler, rewriting the same announcement four times.
Except now you can type this instead:
> "Read the changelog entry I just wrote, draft a launch post for LinkedIn and a shorter one for X (Twitter), and schedule both for Tuesday at 9am."
This guide shows how to connect PostEverywhere to Cursor in about two minutes. Cursor calls PostEverywhere, your posts land in the queue, and you never leave the editor. No copy-pasting, no tab juggling, no scheduler UI.
This works because Cursor speaks the Model Context Protocol (MCP), the same open standard Claude and ChatGPT use for remote tool servers. Point Cursor at the PostEverywhere MCP server and it gains real tools: schedule posts, upload media, generate images, read analytics.
[PostEverywhere](/agents) runs the hosted MCP server that covers Instagram, LinkedIn, TikTok, YouTube, Facebook, X, Threads, Pinterest, Bluesky, Discord and Telegram from one connection. The advantage over running this from a chat window is context: Cursor already has your repository open.
*Written by Jamie Partridge, Founder. Published 21 September 2026.*
## Table of Contents
1. [What you need to connect PostEverywhere to Cursor](#what-you-need-to-connect-posteverywhere-to-cursor)
2. [Why Cursor can post to social media through PostEverywhere](#why-cursor-can-post-to-social-media-through-posteverywhere)
3. [Step-by-step: connect PostEverywhere to Cursor with mcp.json](#step-by-step-connect-posteverywhere-to-cursor-with-mcpjson)
4. [Seven PostEverywhere prompts to try in Cursor](#seven-posteverywhere-prompts-to-try-in-cursor)
5. [What Cursor can actually do with your PostEverywhere accounts](#what-cursor-can-actually-do-with-your-posteverywhere-accounts)
6. [Project config versus global config for the PostEverywhere server](#project-config-versus-global-config-for-the-posteverywhere-server)
7. [Alternative: drive PostEverywhere from the API instead](#alternative-drive-posteverywhere-from-the-api-instead)
8. [Limits, safety and troubleshooting the PostEverywhere connector](#limits-safety-and-troubleshooting-the-posteverywhere-connector)
9. [Connect PostEverywhere to your other assistants](#connect-posteverywhere-to-your-other-assistants)
10. [FAQs](#faqs)
## What you need to connect PostEverywhere to Cursor
Three things, and the first two take longer than the setup itself.
**A recent Cursor installation.** MCP has been in Cursor for a while, but remote servers over Streamable HTTP and browser-based OAuth landed later. If your Settings pane has a **Tools & MCP** section, you are current enough.
**A PostEverywhere account with at least one social account connected.** The MCP server exposes the accounts you have already authorised, so linking Instagram or LinkedIn happens once in the dashboard rather than in the editor. If you are running several brands, [managing multiple accounts](/multi-account-management) explains how that is structured, and agencies usually want [team workspaces](/team-workspaces) configured first.
**About two minutes.** There is no SDK to install, no local process to keep alive, and no client secret to generate.
> **Want the fastest possible start?** [Start a 7-day trial](https://app.posteverywhere.ai/signup), connect two or three accounts, and have Cursor scheduling before your next build finishes. Card required, $0 charged today, cancel anytime.
## Why Cursor can post to social media through PostEverywhere
Cursor is an editor with a very good model attached. It reads your repository, writes code, runs commands you approve. What it does not have is a credential for your Instagram account, or any idea how Instagram's publishing API differs from LinkedIn's.
MCP is the piece that fixes this. It is an open protocol, released in late 2024 and since adopted across the industry, that hands a model a defined set of tools: here is what each one does, here is what it takes, here is what it returns. The model reasons, the server executes. The protocol introduction is worth ten minutes if you want to understand what the model is handed. Our explainer on [what social media AI agents actually are](/blog/what-are-social-media-ai-agents) covers the wider shape of this.
So the division of labour is clean. Cursor decides what to post and when. PostEverywhere holds the authorised account connections, adapts each post to each platform's rules, and publishes through the official API for that network. Cursor never touches Instagram directly, which is exactly why this is safe to set up.
If you want the deeper comparison of protocol versus plain REST, we wrote that up in [MCP versus API for social media](/blog/social-media-api-vs-mcp), and the security question is handled separately in [safe agent access to social accounts](/blog/ai-agent-access-to-social-media).
## Step-by-step: connect PostEverywhere to Cursor with mcp.json
The whole flow is: open settings, paste a block, sign in, prompt.
### Step 1: Open the MCP settings
In Cursor, open **Settings**, then **Tools & MCP**. This is where every MCP server you connect appears, along with the tools each exposes.
### Step 2: Add the PostEverywhere server
Cursor stores MCP configuration in an `mcp.json` file. Add PostEverywhere as a remote server:
```json
{
"mcpServers": {
"posteverywhere": {
"url": "https://mcp.posteverywhere.ai"
}
}
}
```
That is the entire configuration. No command, no args, no environment block, because this is a hosted server rather than something running on your machine. Leave any OAuth client ID and secret fields empty. The server handles sign-in itself.
### Step 3: Sign in
Cursor opens your browser to complete authentication, then stores the credentials for you. Log in with your normal PostEverywhere account. This is the standard OAuth flow, the same one behind "Sign in with Google" anywhere else, which means your password never goes near the editor. The mechanics are the same ones described in our [social media OAuth guide](/blog/social-media-oauth-guide).
### Step 4: Approve the tools
Back in **Tools & MCP**, the PostEverywhere entry lists what it can do: create and schedule posts, list accounts, upload media, generate captions and images, read analytics, manage campaigns and webhooks. All 38 tools become available once approved.
### Step 5: Run a sanity check
Open the chat pane and ask:
> "Show me my connected social accounts on PostEverywhere."
Cursor calls the `list_accounts` tool and returns your linked platforms with their status. If your accounts come back, you are live. Total setup time is usually under two minutes.
For the fuller reference on Cursor's own MCP behaviour, including transport details and project scoping, Cursor's MCP documentation is authoritative.
## Seven PostEverywhere prompts to try in Cursor
The prompts worth running are the ones that use what Cursor already has in context. That is the entire advantage over a chat window.
> "Read the changelog entry I just wrote, draft a launch post for LinkedIn and a shorter one for X (Twitter), and schedule both for Tuesday at 9am."
> "Summarise the last ten commits on this branch into a short build-in-public post and schedule it for tomorrow morning."
> "Take the README intro, turn it into a five-post thread, and queue it across next week."
> "Generate a product-style image for this release and schedule it to Instagram with the caption we drafted."
> "Which of my accounts have not had a post in the last fourteen days?"
> "Did anything fail to publish this week? If so, retry it."
> "Show me next week's queue and tell me where the gaps are."
The last three matter more than the writing ones. Scheduling is easy; noticing a silent failure three days later is what actually costs you, which is why we argue for [webhooks rather than polling](/blog/ai-agents-webhooks-not-polling) and document [what happens when posts fail](/blog/when-social-posts-fail-webhooks).
## What Cursor can actually do with your PostEverywhere accounts
Once connected, Cursor can schedule to a single account or to every account at once, which is what [cross-posting](/cross-posting) handles underneath, and the reason [posting everywhere at once](/post-to-all-social-media-at-once) stops being a manual chore.
It can upload media, write captions through the [AI content generator](/ai-content-generator), produce images with the [image generator](/ai-image-generator) or clips with the [video generator](/ai-video-generator), and read results back from [analytics](/social-media-analytics). It can check the [content calendar](/social-media-calendar) for gaps, consult [best times to post](/best-time-to-post), and drive [bulk scheduling](/bulk-scheduling) from a spreadsheet.
Platform-specific behaviour is handled on our side, so the same tool call works whether the destination is the [Instagram scheduler](/instagram-scheduler), the [LinkedIn scheduler](/linkedin-scheduler), the [TikTok scheduler](/tiktok-scheduler), the [X scheduler](/x-scheduler), the [Bluesky scheduler](/bluesky-scheduler) or the [Telegram scheduler](/telegram-scheduler).
What it cannot do is reply to comments or DMs, because those are not publishing actions and we do not expose them. It also cannot authorise a new social account for you. Connecting a platform stays a deliberate, human, browser-based step, by design.
## Project config versus global config for the PostEverywhere server
Cursor supports two locations for `mcp.json`, and the choice matters more than it looks.
A **project-scoped** config lives at `.cursor/mcp.json` inside the repository, so the server is available only when that project is open. This is right when the social account belongs to the project, for example a single product's brand account, and when teammates in the same repo should inherit the same tooling.
A **global** config lives at `~/.cursor/mcp.json` and follows you into every project. This is right when you are the one posting, regardless of what you happen to be working on.
If you commit a project-scoped config, note that you are committing the server URL only. There is no credential in that file, because authentication happens through OAuth at connect time and the token lives in Cursor. That is a meaningful difference from MCP servers expecting an API key in an environment block, and it is why we built the hosted server this way.
> **Running this across a team?** [Team workspaces](/team-workspaces) let the agent draft into an approval queue rather than publishing directly, which is the setup most agencies land on. [Pricing](/pricing) starts at $9/month with the API and hosted MCP server on every plan.
## Alternative: drive PostEverywhere from the API instead
An agent is not always the right shape. If your publishing logic is fixed, a model in the middle adds latency, cost and a small chance of surprise.
When every release always goes to the same four accounts with the same caption template, call the [social media API](/social-media-api) directly from a script or a CI step. Our [API guide](/blog/social-media-scheduling-api-guide) walks through that and [getting API access](/blog/how-to-get-social-media-api-access) covers the keys.
Most mature setups run both: deterministic publishing for the predictable flow, an agent for the judgement calls. [Building an agent on the API](/blog/build-social-media-agent-api) covers the hybrid.
## Limits, safety and troubleshooting the PostEverywhere connector
**Approve before you trust.** Cursor shows you what the connector can do before it can do anything. Read the tool list once. A model that can publish is a model that can publish something you did not intend.
**Schedule rather than publish immediately** while you are learning the behaviour. Scheduled posts can be edited or deleted through the same tools right up until they go out. Published posts cannot be recalled, because most platform APIs do not offer it.
**Rate limits are real** on both our side and the platforms'. Asking an agent to schedule two hundred posts in one go will meet a limit, and [the limits are documented](/blog/social-media-api-rate-limits). If you are verifying callbacks, [webhook signatures](/blog/verify-posteverywhere-webhook-signatures) covers that, and [worked automation examples](/blog/automate-social-media-posting-api) live separately.
**If the tools do not appear**, the usual causes are a stale Cursor version, malformed `mcp.json`, or an OAuth window closed before the redirect completed. Re-running the connect step resolves nearly all of them.
**If the connection drops**, check that your PostEverywhere subscription is active. The server refuses tool calls from an inactive workspace rather than failing silently, which is deliberate.
## Connect PostEverywhere to your other assistants
The same hosted server works everywhere, so there is no reason to pick just one client. We have guides for [ChatGPT](/blog/connect-chatgpt-to-social-media), [Claude](/blog/connect-claude-to-social-media), [Gemini](/blog/connect-gemini-to-social-media), [Grok](/blog/connect-grok-to-social-media), [Perplexity](/blog/connect-perplexity-to-social-media) and [n8n](/blog/connect-n8n-to-social-media). Developers living in a terminal should read the [Claude Code MCP guide](/blog/how-to-use-posteverywhere-with-claude-code-mcp) instead, and the same server is [listed in Anthropic's connector directory](/blog/posteverywhere-claude-connector).
For the wider landscape, [which social media tools ship a real MCP server](/blog/social-media-mcp-servers) is the honest survey, [the best scheduling tools for AI agents](/blog/best-social-media-scheduling-tools-for-ai-agents) ranks them by agent-readiness, and [the easiest ones to set up](/blog/easiest-ai-agents-for-social-media-management) ranks by documented setup effort. If you are weighing agents against a plain scheduler, [agents versus schedulers](/blog/ai-agents-vs-social-media-schedulers) is the comparison.
> **Prefer a normal interface?** The [social media scheduler](/social-media-scheduler) does everything described here without an assistant involved, and [automation](/social-media-automation) covers the rules-based middle ground.
## FAQs
### What am I actually connecting Cursor to?
PostEverywhere, not the social platforms. Cursor has no social integrations of its own. The MCP server points Cursor at PostEverywhere, which holds your authorised account connections and publishes through each platform's official API.
### Can Cursor really post to Instagram, TikTok and LinkedIn?
Yes, through PostEverywhere, along with Facebook, YouTube, X, Threads, Pinterest, Bluesky, Discord and Telegram. Cursor calls a tool and we handle each platform's formats, media rules and publishing requirements.
### Do I need to know how to code?
No, despite this being an editor. The setup is pasting a four-line JSON block and clicking through a sign-in. Writing the prompts is plain English.
### Which Cursor plan do I need?
MCP is not gated behind a specific tier the way it is on some other clients. What you need is a current version with the **Tools & MCP** settings pane.
### Is there a free PostEverywhere plan for this?
No. Every plan is a 7-day trial with a card required, and there is no free tier. The API and hosted MCP server are included on every plan rather than sold as an add-on.
### Should I use project or global config?
Global if you are the one posting regardless of project. Project-scoped if the social account belongs to that specific product and teammates should inherit the same setup.
### Is it safe to connect my social accounts this way?
Safer than sharing passwords. Cursor never receives platform credentials, only a scoped connection to PostEverywhere that you can revoke from your dashboard at any time.
### What is the difference between this and Zapier?
Zapier fires a predefined automation when a trigger happens. MCP gives a reasoning model a set of tools and lets it decide which to call. The first is a rule, the second is judgement. Most teams end up wanting both.
### Can I run Cursor and Claude Code in the same repo?
Yes. They are separate clients reading separate configs, both pointing at the same hosted server, and neither interferes with the other.
If you are migrating an existing setup, [moving from the Buffer API](/blog/migrate-from-buffer-api-to-posteverywhere) covers the differences. For everything the agent can reach, the [developer docs](/developers) and [connectors directory](/connectors) are the reference.