Content calendars run by agents

WordPress MCP publishes. Versely MCP generates. Adobe Workfront AI Collaborators track the work. The calendar is the job queue those three wires read, not a spreadsheet of intentions.

This is not a primer on Model Context Protocol, and it is not "Astra will run your marketing team." GPT-6 Astra, announced 3 September 2026, is a computer-use and software-engineering model. It can sit on a host and choose tools. It does not render a clip, and it does not make a WordPress post unless a WordPress tool is connected. The sister page on that split is Astra MCP vs WordPress MCP. This page is the editorial object: a calendar that agents can execute without turning the week into a chat.

The calendar is a queue of jobs

Most calendars fail because they store wishes. "Tuesday: thought leadership." An agent cannot execute a wish. An agent can execute a job with a type, an input, a destination, and a human gate.

WordPress.com opened MCP to agents on 20 March 2026 (CMSWire). The point of that server is to write and manage CMS content: posts, pages, the objects a WordPress site already is. Storyblok, Directus, Hygraph, Kontent.ai, and Contentstack also ship MCP servers. Adobe Workfront added AI Collaborators in August 2026 (MarTech's roundup of that wave). Those are content-ops wires. They move entries, assignments, and status. They do not run Veo.

Versely MCP is the generate-and-deliver wire: images, video, audio, captions, slideshows, social posts on connected accounts, workflows. Setup lives on the MCP page. generate spends credits. post is a social post in Versely, not a WordPress wp_insert_post. Mixing those verbs is how a calendar "runs itself" and publishes a paragraph that says "video to come."

A job row a calendar can actually hand an agent looks like this:

Object. Clip, still, captioned cut, WordPress post, Workfront task. One object per row.
Input. The brief, the references, the language, the duration ladder the model actually sells.
Renderer or CMS. A catalog slug, or a WordPress content type, never "make the thing."
Gate. Who watches the file or the draft before it is public.
Destination. TikTok, a blog slug, a campaign folder. Social post and a CMS entry are different destinations.

Standing slots still help — Monday teach, Wednesday product, Friday point of view — but the slot is a type for the queue, not a caption in a cell. The older automation post on this site is about slots as a human system. This page is what changed in 2026: the slot can be filled by a host calling tools, as long as the row is typed.

Volume is not the scarce resource. Teams already report up to 11× more video per month with AI workflows (OpusClip; Hedra; Pictory). A calendar that asks an agent for 11× more undifferentiated files is how you drown a review queue. A calendar that asks for three typed jobs a week, with inputs attached, is how an agent earns its keep.

Three wires, three objects

Keep the wires separate in the brief, in the host config, and in the log.

Versely MCP — media. Named slug, duration, aspect, references. The AI video generator is the same job in the web app; MCP is the same catalog on a wire. If the host "made a video" and the log has no Versely request id, you have a chat artifact. You do not have a studio clip.

WordPress.com MCP (and the other CMS servers) — entries. Title, body, featured media URL, status. The clip has to exist first, or the post is a promise. Hygraph is not WordPress. Storyblok is not Contentstack. The brain has to know which server owns which object. Put that next to the video slugs on the routing card.

Workfront AI Collaborators — the work object. Briefs, assignments, status, the campaign the clip belongs to. August 2026 is the date on that product wave. Workfront is not a renderer and not a CMS. An agent that "finishes the task" by writing a comment has not shipped a file.

Astra, Claude, Fable, Sol — pick the brain your policy allows — can sit in one host with all three servers connected. That is useful only if the user turn names which wire. "Draft the making-of post" is WordPress. "Generate the 8s talking shot on seedance-2-0" is Versely. "Mark the creative task as in review" is Workfront. "Do next week's calendar" with no nouns is how you get a blog post that describes a video nobody made.

Social is a fourth object people smash into WordPress. A scheduled Reel is not an article. If the job is "put this on TikTok," that is Versely's social tools. If the job is "write the article that embeds the clip," that is WordPress. Both can be on Tuesday. They are still two rows.

Computer use, from the Astra launch, is a fifth pair of hands: the Mac, the sheet, the deck. Do not use computer use to click a consumer generate button you do not meter. Use MCP (or the API) for the job object. Sheets are for the calendar the humans still need to see. Generates are for the catalog.

Review is a named slot

An agent-run calendar without a human gate is a syndication engine for cousins of the product.

Skip the watch and you will publish a pack shot that is almost the SKU, a talking line you did not approve, or a caption that collides with the UI. Skip the generate and you will publish "video to come." Skip the CMS step and the clip will live in a folder nobody embedded.

Article 50, in force from 2 August 2026, is the legal version of the same gate for public-interest text: AI-generated text on public-interest topics must be labelled unless it has human review or editorial control that is substantive, not spell-checking. The disclosure template is the copy for the media side. The calendar's review slot is how you have a log that review happened. An agent that publishes straight from generate to WordPress "publish" is not editorial control. It is a hose.

Put the gate on the calendar as a row, not as a vibe:

File exists. Versely job id, duration, language, caption language.
Human watched it. Named person, timestamp, pass/fail. Fail returns to generate with one note, not a new personality.
Label if required. Platform AI label, Article 50 visible label when the clip resembles real people or places that would appear authentic.
Then WordPress MCP or social post.

Workfront is a reasonable place to hang that status if the team already lives there. A spreadsheet is fine if they do not. The tool is not the point. The point is that "in review" is a state an agent can be forbidden to skip.

Cadence belongs here too. A queue that fills Sunday night with 40 files will not be reviewed. Three typed jobs, reviewed, beat twenty unreviewed ones. The retention economy does not pay you for inventory you did not watch.

What stays human

Agents are good at fetching the next row, calling a named tool, and writing the id down. They are bad at deciding that this week's news should kill Wednesday's product clip, that the founder should not say that sentence, that the pack in the still is last season.

Keep human:

The slot types. What a Monday is for. An agent that invents a fourth format every week is a randomiser.
The never-list. Claims, competitors, medical implications, anything legal already wrote down.
The watch. One pair of eyes on the file. Not a committee. Not zero.
The kill. Permission to delete a scheduled row because the world moved.

Let the agent:

Pull the next job from the calendar
Call Versely MCP with the slug already on the row
Draft the WordPress post that embeds a file a human already passed
Flip a Workfront status from "ready to generate" to "in review" to "published"
Remind someone that Thursday's row has no input attached

Do not let the agent pick the renderer "based on vibes" if you have a routing card. Name the slug on the calendar row. A brain allowed to pick will pick the model it saw in a blog post.

Do not let the agent be the studio. GPT-6 Astra will not make your videos. MCP will not either. The catalog will, when called. The calendar is how you call it on purpose, every week, without a scramble.

When the queue should spend credits on named jobs instead of a chat that promises a week of content, sign up, connect the MCP URL, and put slugs on the rows.

FAQ

Can WordPress MCP generate the video if we describe it well enough?

No. WordPress MCP writes and manages CMS objects. A good description becomes a paragraph. Versely MCP (or the web app) is the generate. Connect both if you want one host to do both, and keep the verbs straight.

Where does Adobe Workfront fit if we already have a calendar?

Workfront is the work object: who owns the row, what state it is in, which campaign it belongs to. It is not a replacement for Versely or for WordPress. AI Collaborators, from the August 2026 wave, help move that work object. They do not meter a Seedance take.

Do we need GPT-6 Astra to run this?

No. You need a host that speaks MCP and a brain your policy allows. Astra is one such brain, with computer use attached. Claude, Fable, Sol, or a cheaper planner can call the same tools. The calendar still has to be typed, or no brain will save it.