Write and schedule social posts without leaving Cursor

From commit to post in the same window

Developers who build in public tend to write the post days after the feature, or never. Cursor's agent has the context right now: it can open the files you changed, the README and the release notes. With Postika connected, it can also see your social channels and your calendar, so the post goes on the right day instead of into a notes app.

A common pattern is to end a work session with one prompt: "summarize what we did today for X and Threads, pending approval tomorrow morning." The agent writes two versions that fit 280 and 500 characters, and you review them in Postika over coffee. If you are not familiar with the protocol, our MCP explainer covers it in two minutes.

Global or per project

~/.cursor/mcp.json makes Postika available in every workspace. If you only want one repository to have it, put the same entry in that project's .cursor/mcp.json instead. Inside Postika, keep one project per product so the agent never mixes announcements; it calls list_projects and you can name the one you want.

For a shared machine or a client repo, use a project API key instead of OAuth: it only reaches one Postika project. Create it under Connect AI → Project keys and use the "Copy MCP configuration" button, which includes the Authorization: Bearer ptk_… header.

Limits the agent has to respect

Postika returns each channel's limit, and rejects posts that break it:

• X: 280 characters, up to 4 images.
• Threads: 500 characters, up to 10 images.
• LinkedIn: 3,000 characters, up to 9 images.

Images and videos cannot travel over MCP, so a screenshot or a demo clip is added in the Postika app. Postika does not publish X threads, only single posts. Check any text against every network at once with the character counter.

When to use the API instead

If you want posts to go out from CI on every release without a chat at all, call Postika's REST API from your pipeline with a project key: a POST to /api/v1/posts with content, channel_ids, when and mode. Many teams use both: CI creates a pending post on each tag, and the Cursor agent rewrites it when it needs a human touch. See Postika for developers and the Claude Code guide. Every plan includes MCP and API access (pricing).