Postly MCP is for AI assistants that need to do real publishing work, not just suggest content.
What MCP gives an agent
With scoped Postly tools, an agent can:
- discover organizations and workspaces
- resolve connected publishing targets
- import media
- validate content against destination rules
- create or update posts
- schedule publishing
- inspect activity and analytics
Why MCP is different from direct API usage
MCP is useful when the actor is an assistant such as ChatGPT, Claude, Gemini, or another tool-using agent. Postly stays the secure execution layer while the agent gets a narrow set of governed actions.
Recommended agent workflow
Connect all intended channels in Postly first. Use postly.list_workspaces and postly.list_social_accounts (or postly.resolve_publishing_targets) to discover authorized destinations; never invent channel IDs. Use target_platforms for post targets, not a CSV channels field. On update, supply the complete desired selection to add or remove channels; omit it to keep the existing selection.
Use postly.get_channel_schema for platform limits and postly.validate_post to check text, overrides, settings and destinations before creating or scheduling. Correct over-limit text using a shorter shared version or platform_posts text overrides, then validate again after changing text or channels. CSV preview and Google Sheets also show affected-platform character counts and limits, with manual editing available; see the bulk guide.
- Resolve the right workspace first.
- Fetch the available channels or groups.
- Validate the content if the campaign is complex.
- Attach media during the same flow when possible.
- Create, update, schedule, or inspect the post.
- Report results back to the user clearly.
Where teams usually get value
- turning prompts into scheduled campaigns
- drafting then routing into approval
- handling generated media without manual re-hosting
- summarizing scheduled activity
- turning analytics into next-step suggestions
Guardrails that matter
Keep generation and execution close together
If the agent generates media or receives a temporary file reference, it should pass that media into Postly during the same turn or request flow where possible.
Keep workspace scope explicit
Agents should not guess the publishing destination. Resolve it.
Keep review in place where needed
MCP can speed up operations without removing approvals.
Good next guides
Deletion and accidental live posts
Deleting a post in Postly is separate from removing published content. DELETE /posts/{postId} and postly_delete_post only remove the post in Postly; a successful response does not confirm live removal on any platform. In the dashboard, choose Delete on Platforms for supported destinations before removing the post, and review each result. Unsupported content needs manual action. DEV articles move to drafts rather than being permanently deleted.
Keep the post in Postly and live links until you have verified removal. Do not interpret a publishing notification or an absent post in Postly as a deletion receipt. See platform support, permissions, and the agency recovery workflow.