List your authorized workspaces and connected channels.
Try: “List my Postly workspaces and connected channels.”
Muse + Postly
Use your Postly API access to connect Muse through MCP for workspace discovery, media, publishing, scheduling, and analytics. Publishing with Muse has been tested. The Postly MCP endpoint accepts API keys. Muse directory submission is awaiting review; its native OAuth connection is still being validated.
Publishing tested; API-key connection available. Requires Postly API access and an eligible client account.
Setup reviewed October 25, 2026 · Postly Team
https://mcp.postly.ai/muse. When OAuth is offered, enter your key only on the Postly authorization page. For API-key clients, use Authorization: Bearer <your-api-key> in connection settings.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 →
Postly checks your API key permissions and workspace access for every action. Publishing with Muse has been tested. The Postly MCP endpoint accepts API keys. Muse directory submission is awaiting review; its native OAuth connection is still being validated.
Try: “List my Postly workspaces and connected channels.”
Try: “Upload this image to my Postly Media Library without publishing it.”
Try: “Show publishing status for my selected workspace.”
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.
Check the endpoint and connection method, enable the tools, and start a fresh session. Client plans and administrator settings can affect custom MCP access.
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.
Retrieve the Postly post ID and inspect the schedule, approval state, and destination results. Resolve the specific validation or provider error before retrying.
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.