| 开发者 |
rtCamp
utsavladani iamdanih17 aviral89 hiabhaykulkarni justlevine muralig dipankardas011 jayson31 |
|---|---|
| 更新时间 | 2026年11月2日 19:22 |
| PHP版本: | 6.9 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No. Publishio builds pages from your site's own block patterns and your active theme's styles, so new content inherits your existing layout, spacing, colours, and typography. It doesn't restyle your site, edit your theme, or invent CSS — the AI assembles content from the building blocks your designers already approved. You approve the plan in the chat before anything is written, and nothing goes live until you publish it in WordPress.
Publishio exposes a standard MCP server on your own site at https://your-site.com/wp-json/mcp/publishio (your exact URL is shown on the Publishio dashboard page). In ChatGPT, add that URL as a custom MCP connector and authorize it — Publishio handles authentication with OAuth. The Publishio dashboard includes a step-by-step ChatGPT setup guide alongside the Claude guide.
Open the Publishio page in your WordPress dashboard. It includes a complete, step-by-step guide for adding your site's MCP server to Claude and authorizing the connection.
Open Publishio → Status in your dashboard. It checks your site the way an AI app does and names the step that fails, such as a web server blocking /.well-known/ or a security plugin blocking the REST API, with how to fix it. Copy the report it gives you and send it to your developer, your host or rtCamp, or paste it into Claude or ChatGPT and ask it to walk you through the fix.
Yes — Publishio adds no third-party service. It runs entirely on your own WordPress site as a self-hosted MCP server, and your site connects directly to the AI you choose; nothing is routed through rtCamp or any Publishio-operated cloud. The pages and posts you create live in your own database, exactly like any other WordPress content. The only data that leaves your site is what you send to your chosen AI assistant (ChatGPT or Claude) during a chat — the same as using that assistant anywhere else — governed by that provider's terms.
Yes. Publishio works with any post type that uses the Block Editor — pages, posts, and custom post types (e.g. portfolio, product, event). Featured images, categories, tags and Yoast fields work on every type that has them. Just tell the AI which post type to create.
Yes, if the app supports Client ID Metadata Documents (CIMD), the OAuth sign-in method the MCP specification recommends. Claude (web, desktop, and Claude Code) and ChatGPT support it. Cursor, Gemini CLI, and Windsurf only support the older dynamic client registration, so they can't connect until they add CIMD support.
No, it works with any block-based / FSE theme. Themes with well-described patterns (like Twenty Twenty-Five) yield the best results, because the AI matches patterns from their names and descriptions.
You're always in control. The AI proposes the whole plan, with the pattern for each section, and waits for your yes before it writes anything. In apps that show previews, you see each section as it's added and the finished page with its search and social details; in other apps, the AI shares the preview and editor links. A change to a published page needs your OK in the chat first. The AI can't publish: everything stays a draft until you publish it in WordPress.
Only when you ask, and only unsynced patterns from your pattern library. Pages that already use an unsynced pattern keep their own copy, so they don't change. Synced patterns and your theme's and plugins' patterns are never changed; on a page, the AI can only change a synced pattern's override values for that page.
Publishio is designed for block-based and Full Site Editing (FSE) themes. Classic themes without block editor support are not recommended — the AI generates Block Editor content that requires block-aware themes to render correctly.
No. Publishio generates native WordPress block markup for the Block Editor. Page builder shortcodes and proprietary formats are not supported.