Astra MCP vs WordPress MCP

MCP is the wire; Astra is the brain. Versely MCP generates; WordPress MCP publishes. Do not swap those jobs. GPT-6 Astra, announced 3 September 2026 (TechCrunch), is a computer-use and software-engineering model. It is not a renderer. Model Context Protocol is how that brain calls other products as tools. The mistake of this week is treating Astra as if it grew a catalog, or treating one MCP URL as if it were every product you own.

MCP is a wire, not a model

MCP is a protocol. A server publishes tools with names, descriptions and typed inputs. A host — Codex, Claude, Cursor, a chat connector — reads the list and calls them. The host's model is the brain that decides which tool to call. The server is the hands.

Versely's server lives at https://mcp.versely.studio/mcp. Setup is the MCP page: a custom connector, that URL, a Versely login, consent. What happens when you connect Versely MCP is the OAuth 2.1 sequence in order: metadata, dynamic client registration, authorize, consent, token. The access token's audience is the MCP resource. Scopes are the same eight the API uses. generate spends credits. read lists the registry and talks to agentic routes. A token that only has read will look connected and then 403 when you ask for a clip.

One MCP URL is not a second studio. The host is still a chat. Jobs still meter on the Versely balance. There is no parallel MCP wallet. Naming the renderer in the brief still matters, because Claude or Astra did not become Seedance 2.0 when you pasted the URL.

Astra's role on that wire is judgment and tool choice: read the brief, pick the slug from your routing card, call generate, poll, write the id down. Computer use, from the same 3 September launch, is a different 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.

If the host is Codex, the CLI can write the MCP server into the agent config so you are not pasting URLs by hand. That is wiring. It is not a new brain and not a new catalog.

WordPress MCP publishes; Versely MCP generates

This is the split a content team will actually hit.

WordPress.com added write tools to its MCP server on 20 March 2026 (The Next Web), after launching it read-only: 19 new operations across posts, pages, comments, categories, tags and media. 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 made Workfront AI Collaborators generally available in August 2026 (IT Brief). Those are content-ops and CMS wires. They move words and entries. They do not run Veo.

Versely MCP is a generate-and-deliver wire: images, video, audio, music, captions, slideshows, social posts on connected accounts, workflows. The post scope is social posts in Versely, not a WordPress wp_insert_post. The generate scope is media. The ugc scope is overlays, captions, TTS, background removal.

Astra can sit in the middle of both wires in one host. That is the useful architecture:

Brain (Astra, or Fable, or whatever your policy allows) reads the brief.
Versely MCP creates the clip on a named slug.
A human watches the file.
WordPress MCP (or Contentstack, or Storyblok) files the post that embeds it.

Skip step 3 and you will publish a cousin of the product. Skip step 2 and you will publish a post that says "video to come." Ask WordPress MCP to "make the video" and it will write a paragraph. Ask Versely MCP to "publish the blog" and you will be in the wrong tool list.

The CMS servers are not interchangeable with each other either. A Hygraph model is not a WordPress post. The brain has to know which server owns which object. Put that in the routing card next to the video slugs.

Social post on Versely is a third object: a scheduled Reel or Short, not an article. If the job is "put this on TikTok," that is Versely's social tools, not WordPress.com MCP. If the job is "write the making-of article," that is WordPress. Astra can do both in one conversation only if both servers are connected and the brief says which is which.

Astra as the brain on that wire

OpenAI's 3 September materials put Astra at the front of computer use, software engineering and cyber. TechCrunch reported it beat Sol and Fable on bug finding, terminal tasks and codebase questions. Those are brain jobs: which tool, which arguments, what to do when the tool returns 403.

They are not renderer jobs. Astra was not announced with image, video or audio generation; none appears in TechCrunch's launch report. If the host "makes a video," it did so by calling a video tool. Read the log. If the log has no Versely request id, you did not make a studio clip. You made a chat artifact.

Practical rules for Astra-on-MCP:

Name the slug in the user turn. "Generate on seedance-2-0, 8s, 9:16, native audio, attach these three stills." A brain that is allowed to pick will pick the row it saw in a blog post.
Check scope before you debug the model. 403 OAuth token lacks required scope: generate is a reconnect, not an Astra failure.
Keep computer use off the generate path. Sheets and decks on the Mac. Generates on MCP.
Do not ask Astra to invent durations. The registry is the spec. If the tool schema says 4 / 6 / 8, that is the set.
Log the tool name. mcp__versely__* versus a WordPress tool versus a browser click. You want to see which wire moved.

Enterprise admins should know Astra was off by default in Enterprise workspaces at launch (CSO Online). Connecting Versely MCP does not turn Astra on. Those are two switches. A team can have a working Versely connector on Fable or Sol while they wait for an admin to allow Astra.

Opaque recurrence — Astra obscuring chain-of-thought from monitors, as TechCrunch reported — is an alignment topic, not an MCP topic. It does not change the tool list. It may change whether your security team allows the brain. If they do not, the wire still works with a different brain.

Do not let the host become the renderer

The failure mode is aesthetic: the chat window looks like it made a clip, so the team stops naming models. Then Sora's API shut down on 24 September 2026 (OpenAI deprecations) and nobody can say which remaining row was actually in use, because the host abstracted it.

Fix: every generate tool call includes a slug from the live catalog. Every CMS tool call includes a content type. Every social tool call includes an account. Astra's value is keeping those fields straight across a long session, not erasing them.

MCP, API or web UI is the surface picker. MCP wins when a person is in the conversation and iteration is the job. The API wins when your product is the initiator. The web app wins when review and captions are the job. Astra can be the brain on the first two. It is not a replacement for the third.

When you are ready to spend credits, connect the wire and generate on a named row. Sign in for the account the token will bind to. Paste the MCP URL in the host. Ask for a clip with the slug in the sentence. Keep WordPress for the post that comes after a human said the clip is shippable.

FAQ

If Astra is so good at computer use, why bother with MCP?

Computer use drives a desktop. MCP drives a metered catalog with scopes, a registry and a credit balance. Content teams need the second for generates. Use the first for the shot list.

Can one Astra session talk to Versely and WordPress at once?

Yes, if both MCP servers are connected in the host. That is the point. It is also how you publish the wrong object if the brief does not name the server.

Does connecting Versely MCP make Astra generate video by itself?

No. Astra remains the brain. Versely remains the renderer. The connector is only how the brain's tool call reaches the catalog.