Assign strategy, copy, analytics, and validation roles to a repeatable campaign workflow.
Try: “Run a campaign cabinet: strategist plans, copywriter drafts, analyst reviews, publisher schedules.”
Cabinet + Postly
Manage social media with Cabinet.
Connect Cabinet to Postly's dedicated MCP endpoint so its assistants can work with posts, channels, schedules, analytics, media, approvals, and publishing in a governed workspace.
Custom MCP configuration. Requires Postly API access and an eligible client account.
Setup reviewed October 25, 2026 · Postly Team
Connect Cabinet to Postly
- Connect publishing channels in Postly and select the workspace for your assistant. Check API access in your plan.
- Add the Postly remote endpoint to your Cabinet MCP configuration. Verify workspace discovery before requesting publishing.
- Use
https://mcp.postly.ai/cabinet. When OAuth is offered, enter your key only on the Postly authorization page. For API-key clients, useAuthorization: Bearer <your-api-key>in connection settings. - Start a fresh session, enable Postly tools, and verify your workspace and channels with the read-only task below.
Confirm your first successful connection
List my Postly workspaces and connected publishing channels. Show the workspace and destination names. Do not create, schedule, or publish anything.
Match the result to your intended brand. Check API activity for a successful request, then try a publishing workflow.
Copy a launch, weekly-plan, or content-reuse brief →
Publishing workflows for Cabinet
Cabinet workflows work best when every role has a lane. Postly gives those roles shared context, approved tools, workspace access, activity history, and clear paths from planning to publishing.
Create approval-ready drafts while keeping publishing permissions scoped.
Try: “Create a client launch plan with approval checkpoints and analytics follow-up.”
Generate executive summaries from analytics and publishing activity.
Try: “Summarize campaign performance and assign next actions by role.”
Before a write action, confirm content, media, workspace, destinations, date, time, and timezone. Use team approvals where required. Keep the returned post ID and inspect its destination status; accepted or scheduled does not mean published.
Scheduled agent runs depend on your assistant’s orchestration. For recurring source-based publishing, use Auto Post. Your editor and calendar remain available throughout.
Connection and publishing help
No Postly tools appear
Check the endpoint and connection method, enable the tools, and start a fresh session. Client plans and administrator settings can affect custom MCP access.
The workspace or channel is missing
Check the allowed workspace named in the error. Use its workspace ID, switch to the correct API key, or edit Workspace access in API keys. Reconnect a channel if its provider authorization expired.
An accepted request has not published
Retrieve the Postly post ID and inspect the schedule, approval state, and destination results. Resolve the specific validation or provider error before retrying.
How do I stop the connection?
Disable the client connection and revoke its API key in Postly. Review scheduled posts separately; revoking a key does not cancel already accepted publishing work.