A response is not a publication
accepted, requires_approval and scheduled are workflow states. Keep the returned post ID and read it with get_publish until each destination reports published or failed.
Cursor
Add Postdom as a Cursor MCP server and Cursor's agent can check your connected accounts, submit finished videos for your approval and read what published, while Postdom keeps every result.
Updated
Postdom's hosted MCP server at https://api.postdom.com/mcp has all 17 tools, including create_slideshow, which makes a slideshow on your brand kit from slides your agent writes. Nothing to install: clients that support MCP sign-in connect to your workspace, and any client can send a workspace key instead.
Add the hosted server to Cursor (.cursor/mcp.json)
{
"mcpServers": {
"postdom": {
"url": "https://api.postdom.com/mcp"
}
}
}| Tool | What it does | Reads or writes |
|---|---|---|
get_workspace_status | Start here to read setup progress, connection availability, accounts, policy, brief, and activity counts. | Reads |
list_accounts | List destination account IDs and connection state, synchronizing provider state into Postdom for this workspace. | Writes |
connect_account | Create a platform authorization URL for a human to complete when the workspace connection gate is unlocked. | Writes |
get_brief | Read the current workspace-owned brand guidance before planning or writing content. | Reads |
get_digest | Read the latest completed workspace week as descriptive evidence. | Reads |
get_learning | Read shared account learning: source-linked observations and exploratory advice for one learning scope. | Reads |
upload_media | Create a short-lived direct-upload contract for finished video or image bytes. | Writes |
get_media | Verify one uploaded media handle before publishing it. | Writes |
submit_plan | Propose a time-bounded publication plan for one human approval. | Writes |
get_plan | Read the current plan state and structured feedback from the human reviewer. | Reads |
publish_video | Submit finished media for immediate or UTC-scheduled execution using the current-source publish_video contract. | Writes |
get_publish | Read one post state, every destination outcome, and structured approval feedback. | Reads |
list_posts | List this workspace's posts to answer what is scheduled without already holding a post ID. | Reads |
get_performance | Read normalized measurements for one post or one connected account. | Reads |
get_best_posts | Rank one account's posts by one evidence-backed metric over a requested window. | Reads |
create_slideshow | Render carousel slides on the workspace brand kit from words and images, and store each slide as image media. | Writes |
account_music | Read or set who adds the music on each connected account, and read where each handed-off video stands. | Writes |
Sign up and your API key is in Settings, Connected apps. The REST API, MCP server, SDKs and webhooks are on every plan. Starter, Growth and Scale start with a 7-day free trial.
Cursor reads MCP servers from .cursor/mcp.json. This block names an environment variable and holds no key.
.cursor/mcp.json
{
"mcpServers": {
"postdom": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@postdom/mcp@0.4.0"],
"env": { "POSTDOM_API_KEY": "${env:POSTDOM_API_KEY}" }
}
}
}Put Postdom's operating brief in .cursor/rules/postdom.mdc so the agent loads the rules with the project. The package needs Node.js 22 or newer.
Starter, Growth and Scale start with a 7-day free trial, so you can see posts made from your website before you pay. Cancel anytime. After the trial, Starter is $39 a month for 30 posts.
The MCP server, the REST API, the SDKs and webhooks are included on every plan. Your own agent uses its own model.
Through the hosted server, Cursor gets 17 tools: workspace status, accounts, the brief, slideshows made on your brand kit, uploads, plans, publishing, and reading results and performance. The local package @postdom/mcp@0.4.0 has the original 14.
A Cursor MCP server is a server that gives Cursor's agent extra tools through the Model Context Protocol, so it can act outside your code, such as posting a video.
Over MCP, your agent can make slideshows and publish them: create_slideshow draws the slides your agent writes on your brand kit, and publish_video posts them or a finished video you supply. The videos Postdom writes from your website are made in the app, and every post waits for the approval its account needs.
accepted, requires_approval and scheduled are workflow states. Keep the returned post ID and read it with get_publish until each destination reports published or failed.
You own the accounts, the rules and the approval. Your agent prepares the request; you decide what goes out.
When a platform does not report a value, Postdom marks it unavailable with the reason, and leaves it out of totals.
Related: Claude Code MCP server and Codex MCP server.
Yes. The hosted server gives Cursor 17 tools, and the local package @postdom/mcp@0.4.0 runs over stdio with the original 14.
Any of them. MCP access is included on every plan.
In .cursor/rules/postdom.mdc. It tells the agent how to work; it is not the connection.
No. The agent prepares the request; a person approves it in Postdom.
Sign up, then create a key in Settings, Connected apps. The same key works with the REST API, the MCP server and the SDKs.
The REST API, MCP server, SDKs and webhooks are on every plan. Starter, Growth and Scale start with a 7-day free trial.
Start your free trial, connect Cursor, and let Postdom make your posts from your website too.
Starter, Growth and Scale start with a 7-day free trial.