# Cursor MCP: Post to Social Media From Cursor **Source:** https://posteverywhere.ai/connectors/cursor --- # Ship a release and announce it without leaving Cursor Yes, on a paid Cursor plan. MCP servers are not available on the free Hobby tier, so there is no section to add this to. Cursor speaks the Model Context Protocol, so it can use PostEverywhere the same way Claude or ChatGPT does. Add the hosted server once and you can ship a release and announce it without leaving the editor. Two things trip people up. MCP is not on the free Hobby tier, so if you cannot find where to add a server that is why. And the setting moved: it is under Customize in the sidebar now, not under Settings where most older guides still send you. Because Cursor keeps the server registered per user rather than per project, you set it up once and it follows you into every repository. That matters more than it sounds when the announcement always seems to be needed from whichever project you are not currently in. [Start your 7 day trial](https://app.posteverywhere.ai/signup)[All connectors →](https://posteverywhere.ai/connectors)Card required · $0 charged today · cancel any time ## How to connect PostEverywhere to Cursor No server to run locally and no config file to hand-edit. Add it once and it persists across projects. Before you start - A paid Cursor plan. MCP is not part of the free Hobby tier, so there is no section to add a server to. - Node installed and on your PATH, because the local server path runs through npx. - A PostEverywhere plan for the API key, plus at least one authorised social account. Cursor needs a paid plan for MCP MCP servers are not on the free Hobby tier. On Hobby there is no MCP section to add this to. - 1Open Customize in the Cursor sidebar. It is no longer under Settings. - 2Paste https://mcp.posteverywhere.ai. - 3Approve the sign-in window Cursor opens. Building something custom? See [the Cursor config reference](https://posteverywhere.ai/docs/integrations/mcp#connect-the-mcp-server-to-cursor). ## What you can ask Cursor once it is connected Cursor earns its place here by removing the context switch: you ship, then you announce, without leaving the window. Each one maps onto a real tool, covering scheduling, [AI captions](https://posteverywhere.ai/ai-content-generator) and [analytics](https://posteverywhere.ai/social-media-analytics). The [AI agents page](https://posteverywhere.ai/agents) has the full surface. Announce a release from the same window you tagged it in Post a changelog entry to X and LinkedIn without leaving the editor Queue a launch thread while the pull request is still open Check what is already scheduled before you ship, so nothing clashes Turn a commit message into a build-in-public update Retry a failed post without switching to a browser The publishing tools sit alongside Cursor's own, so the agent can treat scheduling as one step of a longer task: finish the change, write the note, put it in the queue. ### What the tools cover You get the full 38 tools, not a cut-down editor subset. Scheduling and cross-posting are the obvious ones, but account health is the quietly useful one for a developer workflow: a disconnected account is the most common reason a scheduled release post silently does not appear, and you can check it from the same window before you ship rather than discovering it the next morning. ### Prompts that work, and what comes back “I have just tagged v2.1. Write a release post and schedule it for 9am, LinkedIn and X.” Cursor reads the context you are already in, drafts the announcement and queues both versions. “Check nothing is already scheduled for tomorrow morning before you add this.” It queries the queue first and tells you what is there, so a launch post does not land on top of something else. “Turn the last five commit messages into one build-in-public update.” It summarises the work into a single post rather than a changelog dump, then schedules it. ## Cursor MCP troubleshooting The three things that actually go wrong, and what fixes each one. There is no MCP section anywhere in Cursor MCP is not included on the free Hobby tier. On a paid plan it appears under Customize in the sidebar, not under Settings where older guides point. The server is listed but shows a red dot Cursor could not start it. Check that Node is installed and reachable, since the local path shells out to npx, then reload the window. The agent ignores the tools Tool use has to be available in the mode you are in. Ask directly in agent mode, naming the action, rather than hoping it infers that publishing is wanted. ## What it will not do Worth knowing now rather than after you have started a trial. - It only works while Cursor is open. This is an editor integration, not a background scheduler; posts you have already queued still publish on our side regardless. - It does not replace the dashboard for bulk work. For a CSV of a hundred posts, bulk scheduling is the better route. - It will not choose your posting times for you. It schedules what you ask, when you ask. ## When to use Cursor rather than another client Cursor is the right choice when the announcement should happen in the same window as the work. If you are already tagging a release there, adding the post is one prompt rather than a context switch. Reference material: [Cursor's MCP documentation](https://docs.cursor.com/context/model-context-protocol), [The Model Context Protocol spec](https://modelcontextprotocol.io). The full agent surface, including the REST API, is on the [AI agents page](https://posteverywhere.ai/agents). ## Included on every paid plan from $9/mo Cursor needs a paid plan for MCP, which is their requirement. Ours is on every plan from $9 with no developer tier. One key covers the connector, the [REST API](https://posteverywhere.ai/social-media-api) and the SDK. Not working in Cursor today? [See all connectors](https://posteverywhere.ai/connectors), wire it up from [n8n, Make or Zapier](https://posteverywhere.ai/integrations), or read how the whole [agent setup](https://posteverywhere.ai/agents) fits together. [Start your 7 day trial](https://app.posteverywhere.ai/signup) ## Cursor MCP FAQ ### How do I connect PostEverywhere to Cursor? Open Customize in the Cursor sidebar. It is no longer under Settings. Then: Paste https://mcp.posteverywhere.ai. Then: Approve the sign-in window Cursor opens. MCP servers are not on the free Hobby tier. On Hobby there is no MCP section to add this to. ### Can Cursor post to social media? Yes, on a paid Cursor plan. MCP servers are not available on the free Hobby tier, so there is no section to add this to. Cursor earns its place here by removing the context switch: you ship, then you announce, without leaving the window. ### Why can I not find the MCP section in Cursor? Two likely reasons. MCP is not available on the free Hobby tier, so there is nothing to add a server to. And the setting moved out of Settings into Customize in the sidebar, which is where most older guides still send you. ### Does this work in Cursor agent mode? Yes. Once connected, the tools are available to the agent like any other MCP tool, so it can schedule a post as one step of a longer task rather than as a separate errand. ### Can I use the same setup in Windsurf, Cline or Zed? Yes. They all speak the Model Context Protocol, so the same hosted URL works. Zed nests it under context_servers and Codex CLI uses TOML, and the per-client config blocks are on the agents page. ### What does it cost to use Cursor this way? Cursor needs a paid plan for MCP, which is their requirement. Ours is on every plan from $9 with no developer tier. Every plan has a 7-day trial and a card is required to start it. ## Other assistants [Claude](https://posteverywhere.ai/connectors/claude)[ChatGPT](https://posteverywhere.ai/connectors/chatgpt)[Claude Code](https://posteverywhere.ai/connectors/claude-code)[Grok](https://posteverywhere.ai/connectors/grok)[Windsurf](https://posteverywhere.ai/connectors/windsurf)[Cline](https://posteverywhere.ai/connectors/cline)[Zed](https://posteverywhere.ai/connectors/zed)[Codex CLI](https://posteverywhere.ai/connectors/codex-cli)