Skip to content

OpenAI Dots + Postly

Manage social media with OpenAI Dots.

Use your Postly API access to connect OpenAI Dots through MCP for workspace discovery, media, publishing, scheduling, and analytics. Custom connections have passed workspace, channel, media upload and publishing tests. Package review is separate from manual setup.

Publishing tested; package review separate. Requires Postly API access and an eligible client account.

Setup reviewed October 25, 2026 · Postly Team

Connect OpenAI Dots to Postly

  1. Connect publishing channels in Postly and select the workspace for your assistant. Check API access in your plan.
  2. Add a custom Postly MCP connection in your supported OpenAI environment and complete Postly authorization. Custom setup is separate from package review.
  3. Use https://mcp.postly.ai/dots. 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.
  4. 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 OpenAI Dots

Postly checks your API key permissions and workspace access for every action. Custom connections have passed workspace, channel, media upload and publishing tests. Package review is separate from manual setup.

List your authorized workspaces and connected channels.

Try: “List my Postly workspaces and connected channels.”

Upload media and check publishing status.

Try: “Upload this image to my Postly Media Library without publishing it.”

Review content and destinations before scheduling.

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.

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.

Guides and references