Let an approved AI assistant schedule posts safely.
Publishly includes the connection an AI assistant needs to publish, schedule, check receipts, and find accounts that need attention — with access you control.
Publishly includes a built-in MCP (Model Context Protocol) server — it starts with the app, with no extra plugin to install. A compatible assistant can publish, schedule, read delivery receipts, and check account health. Every action stays inside the workspace and permissions you approved.
What MCP is
MCP is a common way for an AI assistant to use approved tools in another product. In Publishly, it means the assistant can schedule or check a post without pretending to be a person clicking through the site.
What you can do with it
Drive publishing from wherever you already work with an assistant: publish now, schedule a checked post, ask what happened to it, or find disconnected accounts. Every action stays inside the approved workspace and leaves the same proof as work done in the dashboard.
How to set it up
Choose how the assistant signs in
Use the guided OAuth connection or an API key. Give the assistant read-only access, posting access, or both — and revoke it whenever you want.
Point your assistant at the Publishly MCP endpoint
Add the Publishly connection shown in the API docs. Keys stay out of the web address and logs.
Ask for what you want, in plain language
Ask it to publish now, schedule for later, check a post’s receipt, or find the brand, client, or location accounts that need attention. Publishly still checks ownership, platform rules, and plan limits.
Keep proof for every post
Every scheduled post still gets a delivery receipt and a failure reason. Letting an assistant help never removes the checks.
Endpoint paths and connection specifics live in the API docs — they’re versioned with the backend, so this page stays honest by not duplicating them.
Common questions
Is the MCP server an add-on or a separate product?
Neither. The MCP server starts with the Publishly backend itself. If you run Publishly, you have it.
Which assistants can connect?
Any client that speaks the Model Context Protocol. Publishly implements the server side of the open standard and doesn’t gate specific assistants.
Can an assistant post something my workspace hasn’t authorized?
No. MCP access is authorized per workspace, scoped per tool, and revocable. A read-only key cannot call publish_post or schedule_post, and cross-workspace resource IDs are rejected.