What is the Classic Editor MCP server?
The Classic Editor MCP server from AcrossAI lets Claude, ChatGPT, Cursor and any other MCP client see which editor each post opens in and why, and change the default editor on your WordPress site. It runs inside WordPress through the free Abilities Manager and MCP Manager plugins, and works through Classic Editor itself — with no third-party relay in between.
Looking for another plugin? Browse all WordPress MCP integrations or the Editor integrations.
What your AI can do with Classic Editor
Classic Editor decides which editor opens through four layers: the site default, each user’s own choice, what each post remembers, and what each post type supports. These abilities let an AI assistant read every layer, explain which one won, and change the settings safely.
See which editor wins, and why
Read the effective default, whether users may choose, and the layer that decided it — not just the raw options.
Explain any single post
Find out which editor a post opens in, and whether a remembered choice is being honoured or ignored.
Check post type support
See which post types can use the block editor at all, before anyone changes a setting that cannot help.
Change the default safely
Switch the site default or the per-user choice through Classic Editor’s own validators. Changing the default needs confirm.
Troubleshooting
Post still opening in the wrong editor? Three reasons it happens quietly.
None of these shows a warning in wp-admin. The setting looks right and the post opens in the other editor anyway.
User switching is off
With switching off, a post’s remembered choice is ignored and it opens in the site default. get-post-editor reports when this is happening.
The post remembers its last editor
With switching on, a post reopens in the editor it was last edited in, whatever the default says. get-post-editor names the remembered value.
The post type can’t use blocks
A post type that isn’t block-editor eligible always opens in the classic editor. get-post-type-editor-support shows which ones.
Try asking
Paste one into Claude, ChatGPT or Cursor once your site is connected.
“Which editor are authors getting on this site, and why?”
“Why does the About page keep opening in the classic editor?”
“Which post types can’t use the block editor?”
“Make the block editor the default, but let authors switch back if they want.”
“List every post that’s pinned to the classic editor.”
“Turn off the editor switch so everyone uses the same editor.”
AcrossAI vs WPVibe vs Novamira for Classic Editor
Three ways to connect an AI assistant to Classic Editor. The difference is where the MCP server runs and what sits between your AI and your site.
| AcrossAI | WPVibe | Novamira | |
|---|---|---|---|
| Where the MCP server runs | On your WordPress site | Hosted gateway at mcp.wpvibe.ai | On your WordPress site |
| Third-party relay | None | Every call passes through WPVibe’s cloud | None |
| How it works with Classic Editor | Dedicated Classic Editor abilities, each labelled read-only, write or destructive | Plugin abilities, REST API and WP-CLI | General PHP access; no dedicated Classic Editor specialization listed |
| Designed for | Production sites, with risky changes gated behind confirm | Any host reachable over HTTPS | Dev and staging environments with backups |
| Price | Free, including every Classic Editor ability | Free plan with a daily action allowance; paid tiers | Free core; specializations in Novamira Pro |
Based on each product’s own published documentation, September 2026.
Classic Editor + AI questions
Is there an MCP server for Classic Editor?
Yes. AcrossAI turns your WordPress site into an MCP server with dedicated Classic Editor abilities, so Claude, ChatGPT, Cursor or a local model can work with Classic Editor directly. It’s free on WordPress.org.
Can ChatGPT or Claude manage Classic Editor?
Yes, once your site is connected over MCP. Ask in plain English and your AI calls the Classic Editor abilities on this page, with risky changes gated behind an explicit confirm.
Is the Classic Editor integration free?
Yes. All of its abilities ship in Abilities Manager, which is free on WordPress.org.
Can the AI switch everyone to a different editor by accident?
No. Changing the site-wide default editor refuses to run without an explicit confirm. Reading settings and allowing or disallowing user choice do not need it.
Does it work on multisite?
Yes. On multisite the result also reports whether the network has locked per-site settings, which overrides anything set on the site.
Which AI assistants work with it?
Any MCP client: Claude, ChatGPT, Gemini, Grok, Cursor, Claude Code, and local runtimes such as Ollama, LM Studio and Open WebUI.
Does my site data pass through AcrossAI’s servers?
No. Your WordPress site runs the MCP server and your AI client connects to it directly. There is no hosted gateway in the middle.
Is AcrossAI affiliated with Classic Editor?
No. AcrossAI built and maintains this integration independently, using Classic Editor’s public APIs.