The past two weeks were our biggest sprint yet. We shipped 58 changes to Publisher, and a few of them change how you can work with the product entirely. Here are the headlines, grouped by theme.
Connect your AI assistant with the new MCP server
This is the main feature of the release. Publisher now ships a full Model Context Protocol (MCP) server, so AI clients like Claude can work directly inside your workspace. The connection runs through secure, token-authenticated tools, which means the assistant acts on your content with the same permissions and boundaries you set, not through a side door.
Access is token-based, with a per-organization enable flag, granular permissions, and strict organization isolation. The server is self-documenting, so an agent can discover the full catalog of what it’s allowed to do on its own, without you hand-feeding it instructions.
The tool suites cover most of what you’d do by hand:
- Draft and edit articles, and read or edit the source material behind them
- Create platform-specific social posts
- Manage schedules and timeslots, publish content, and handle approvals
- Browse media and read the dashboard
Agents are brand-aware. They can read your organization’s brand kit and are instructed to write on-brand rather than in a generic house style. Image generation is built in, with cover images saved directly onto articles. For WordPress, the tools can create categories and tags, and they convert HTML into native Gutenberg blocks instead of pasting raw markup.
On the admin side, there’s a token management UI with modal creation, per-call usage logging, and a filter for revoked tokens, so you can see exactly what an agent did and cut off access when you need to.
Pipelines turn queued material into published content
Organization admins can now configure end-to-end content pipelines. Queued source material – links, files, or notes – moves through to published content automatically, without someone shepherding each step.
The flow has four stages: Queue, Process, Approval Gate, then Channels. It reuses the parts of Publisher you already know – extraction, AI drafting, WordPress publishing, and social scheduling – and connects them into one path.
Each pipeline sets its own publish mode. You can drop social posts into a schedule’s timeslots, or publish immediately once a piece is approved. WordPress publishes first, so the final article URL is woven into the social copy automatically rather than left as a placeholder. Submission is role-based, and the pipeline sends notifications on approval and on failure so nothing stalls silently.
WordPress publishing and scheduling, rebuilt
We reworked how Publisher talks to WordPress. You can now schedule WordPress articles with two-way sync between the two systems, so a change in one is reflected in the other.
Publishing is idempotent everywhere. Retries and reschedules no longer create duplicate posts. You can edit already-published posts in place, and Publisher self-heals stale WordPress post references when you reschedule, so a broken link to an old post ID doesn’t break the job. As with the MCP tools, HTML is converted to clean Gutenberg block markup on the way out.
AI image generation
Image providers are now pluggable, and the system supports reference images as input. It also handles AI models that do both text and image generation in one place. When a generation fails, the error is surfaced clearly instead of leaving you guessing why an image didn’t appear.
Workflow and calendar changes
Assignees get a new My Tasks view that collects the work waiting on them. On the publishing calendar, pending-approval posts now show their scheduled time, so you can see when something will go out before you approve it.
Connection health you can trust
Publisher now runs live, read-only API pings to verify the real health of each platform connection. The status you see reflects an actual check rather than an assumed state, so a connection that has quietly gone bad shows up as broken instead of looking fine.
Platform and interface
Publisher now supports Progressive Web App (PWA) install, so you can add it to your device like a native app. We consolidated the Organization and Admin navigation into a single Settings menu. And we strengthened the content prompts to avoid the usual AI writing tells, which makes the generated output read more naturally.
Several of these features build on each other. The MCP server, pipelines, and the WordPress rebuild all share the same publishing and conversion code underneath, which is why they behave consistently whether a person or an agent triggers them. Try them out, and let us know what you ship.
Share this article
