Launching with Cursor

Post to social media from Cursor

Add Postnavo as an MCP server in Cursor and your editor agent can schedule launch posts, build-in-public updates and changelog threads without switching apps.

Cursor at a glance

From the Cursor documentation, read on 2026-10-12. Postnavo is not released yet, so none of this was run against it.

Config file: .cursor/mcp.json in a project, or ~/.cursor/mcp.json for every project.[1]
Transports: stdio, SSE and Streamable HTTP, with OAuth for servers that require it.[1]
On and off: From Customize in the sidebar.[1]
Before a tool runs: Cursor asks for approval by default. The arrow next to the tool name shows the arguments.[1]
In a company: Enterprise admins can allowlist remote servers by URL pattern.[1]
Unattended: Automations run cloud agents on a schedule or on events.[3]

How to connect Cursor

Illustrative — final endpoints and commands are published at launch.

Create .cursor/mcp.json in your project, or ~/.cursor/mcp.json in your home directory to have the server everywhere.[1]
Under mcpServers, add a named entry whose url is the Postnavo MCP server URL (https://mcp.postnavo.com — final URL confirmed at launch).[1]
Open Customize in the sidebar, check the server is enabled, and sign in to Postnavo when Cursor starts OAuth.[1]
Ask the agent to schedule a post. Cursor shows the tool call and waits for your approval.[1]

Connects viaMCP server

Cursor’s mcp.json, approvals and automations

One JSON file, for a project or for everything

Cursor reads custom MCP servers from mcp.json. A file at .cursor/mcp.json gives one project its own tools, and ~/.cursor/mcp.json makes them available everywhere.[1]

A remote server is an entry with a url and, optionally, headers. Values can use ${env:NAME}, so a token is read from your environment instead of sitting in the file.[1]

Postnavo is launching with OAuth sign-in on a hosted server, so its entry holds an address and no key. The MCP server page shows the shape of the file.

Approval before each tool call, unless you change the run mode

“Cursor asks for approval before using MCP tools by default.” You can click the arrow next to the tool name to see the arguments first.[1]

MCP follows the same Run Modes as terminal commands. In Auto-review mode, allowlisted MCP tools run immediately and everything else is routed through the classifier.[1]

The arguments are the useful part for a post: you read what the agent is about to send before it leaves the editor. Postnavo is launching with its own approval setting for the cases where nobody is reading.

Teams: a marketplace and an allowlist

Team admins can distribute MCP servers through a team marketplace. Enterprise admins can also control which servers users may run, under Team Settings, MCP Configuration.[1]

Remote servers are approved by URL pattern, and a tool allowlist can restrict which tools of an approved server run automatically. Cursor notes that allowlisting approves a configuration and does not install the server.[1]

If your company restricts servers this way, ask your admin to add the Postnavo address. The final one is published at launch.

Skills in Cursor

Cursor loads Agent Skills from .agents/skills/ or .cursor/skills/ in a project and from ~/.cursor/skills/ for your user. For compatibility it also reads .claude/skills/ and .codex/skills/. You run one by typing / in Agent chat.[2]

This page covers MCP, the route Postnavo is launching with for Cursor.

Automations and cloud agents

Cursor Automations run cloud agents in the background, on a schedule or in response to events from GitHub, GitLab, Slack, webhooks and Linear. An automation can be given tools from MCP.[3]

A scheduled trigger takes a preset or a cron expression, and “may run with a delay but will not start before the indicated time”.[3]

Cloud agents run in isolated VMs and support MCP servers.[4]

So a “pull request merged” automation could draft the announcement. A trigger that may run late is the wrong tool for an exact publish minute: put the time on the post, and the calendar Postnavo is launching with keeps it.

Example prompts

Try asking“Share these release notes on LinkedIn and X tomorrow morning.”
Try asking“Write a build-in-public post about the feature in this diff and schedule it for 5pm.”
Try asking“What do I have scheduled this week? Put it in a table.”

FAQ

Frequently asked questions

Is Cursor integration available now?

Not yet. Postnavo is launching soon with a hosted MCP server, which is how Cursor connects. Join the waitlist to get access first.

Where does the Postnavo entry go in Cursor?

In .cursor/mcp.json for one project or ~/.cursor/mcp.json for all of them, as a named entry with the server URL. The final URL is published when Postnavo launches.

Will Cursor post without asking me?

Cursor asks for approval before using MCP tools by default and lets you read the arguments. In Auto-review mode allowlisted tools run immediately. Postnavo is launching with its own approval setting on top.

My company restricts MCP servers in Cursor. Can I still connect?

Cursor’s Enterprise admins approve remote servers by URL pattern, so ask yours to add Postnavo’s server address. It is published at launch.

Sources, checked 2026-10-12

Get your weekends back. Let AI handle your social.

Join the waitlist and lock in 30% off for life.

Founding price for life
No credit card
Unsubscribe anytime