planpo.st
FeaturesFor AI agentsRevenue trackingPlatformsPricingBlogSupport
Sign inStart free trial →
planpo.st

Social scheduling with revenue built in. One platform for creators and businesses who treat social as a growth engine.

Planpo.st on Nick Launches

Product

SchedulerFor creatorsFor agenciesCompare toolsAlternativesPricing

Channels

InstagramLinkedInX (Twitter)ThreadsFacebookYouTubeTikTokAll channels →

AI agents

MCP serverFor AI agentsClaude CodeCursorChatGPTGemini CLIAll agents →

Revenue

Revenue trackingRevenue attributionStripeShopifyRevenueCatAll integrations →

Resources

DocsMCP toolsAPI referenceBlogAboutSupportContactPrivacyTerms

Compare planpo.st

  • planpo.st vs Postiz
  • planpo.st vs Buffer
  • planpo.st vs Hootsuite
  • planpo.st vs Later
  • planpo.st vs Sprout Social
  • planpo.st vs SocialBee
  • planpo.st vs Planable
  • planpo.st vs Metricool
  • planpo.st vs Loomly
  • planpo.st vs Publer
  • planpo.st vs Post Bridge
  • planpo.st vs Mixpost
  • planpo.st vs Blotato
  • planpo.st vs Typefully
  • All comparisons →
  • Alternatives →
© 2026 planpo.st · all rights reservedstatus: ● all systems normal
  1. Home
  2. /AI agents
  3. /Cursor

Ship the feature, then let Cursor post about it.

The best time to write about a feature is the moment you finish it, and the worst place to do that is a browser tab with seven half-filled compose boxes. If you build in Cursor, the fix is one MCP entry: planpo.st becomes a set of tools your agent can call mid-session.

Cursor's agent already knows what changed, it has the diff in front of it. Handing it a scheduler means the announcement gets drafted while the context is still warm, and the tracked link means you find out later whether that announcement sold anything.

Start 7-day free trial →Setup instructions

What Cursor is

Cursor is the AI code editor built on VS Code, and its agent mode has first-class MCP support with a JSON config per project or global. It is where a lot of indie products get built, which makes it a natural place for those products to get announced too.

Three things to try on day one

1. Announce what you just merged

Summarize this PR for a non-technical audience and schedule it as a post on X and LinkedIn tomorrow morning, link to the changelog.

The agent writes two versions sized to each network, wraps the changelog URL in a tracked link, and calls create_post with a morning slot. The queue shows both drafts with the diff-accurate description, because the agent read the actual code.

2. Keep a launch thread honest

Draft a 5-post X thread about how we built the export feature, using the actual file names and numbers from this repo, schedule for Saturday.

Threads are a native post type on planpo.st, so the agent creates one thread with five segments, real details from the codebase, and one tracked link at the end. Saturday morning it goes out as a proper thread, not five loose posts.

3. Check whether build-in-public pays

Pull revenue per post for the last 30 days and tell me which topics converted.

get_revenue_overview returns attributed revenue per post, the agent groups it by topic, and you get an answer grounded in payments rather than impressions. Next sprint's announcement gets written with that in mind.

The part the other schedulers skip

Plenty of tools let an agent post. The difference here is what comes back: every link in a scheduled post can be tracked, payments from Stripe, Shopify or RevenueCat are matched to the exact post that caused them, and your agent can read those numbers with the same connection it used to publish. Cursor does not just post for you, it finds out whether the post worked.

How revenue attribution works

Connecting takes a minute

The AI code editor. Config is per project or global. Grab an API key from Settings, add the server, hosted or local, and the tools appear. The full config, with the sharp edges called out, is on the setup page.

Cursor setup guide

Questions people ask

Project config or global config?
Global (~/.cursor/mcp.json) fits most people. A project-level .cursor/mcp.json gets committed with the repo, so if you go per-project, use the hosted URL with an environment variable rather than pasting your API key into a tracked file.
Can it post without asking me?
Only if you tell it to. Cursor shows tool calls before running them by default, and on the planpo.st side you can keep everything as drafts or route posts through approvals, so autonomous publishing is opt-in twice over.
What about media?
upload_media takes images and video, and generate_carousel builds carousel graphics from text. X is the exception: our X publishing is text-only right now, and the compose validation says so rather than failing at publish time.
Does this work with Cursor's background agents?
Anything that runs with your Cursor MCP config can call the tools. The practical pattern is an agent that finishes a task, then queues the announcement as a draft for you to approve.

Keep going

Other agents

Claude CodeClaude DesktopChatGPTGemini CLIAll agentsThe MCP server

What Cursor can reach

The 7 networksPayment integrationsRevenue attribution