Documentation
Finish the conversion with a real editor check, a public page and an evidence-based follow-up.
Use real xSpeed reports without mixing device scores, partial tests or unrelated measurements.
An optional performance follow-up that starts with your site’s existing cache and a reversible baseline.
Three connections with different jobs. Know which one measures, which one converts and which one can change cache settings.
What becomes public, what stays private, and how free-plan listing works.
From a source design to a separate WordPress draft, with checks at every step.
Establish a verified connection without sharing your WordPress password.
Claude.ai, ChatGPT web, Codex, Claude Code and other MCP clients. Choose your client, sign in and verify your site.
Add a custom connector and approve access in AI2WP.
Connect a remote MCP app using browser sign-in.
Use the same account connector as Claude.ai.
Add the HTTP server, then sign in through your browser.
Add the remote server and authenticate with /mcp.
Use OAuth when supported, or a scoped manual token.
What AI2WP checks, what it records, and where its control ends.
Use a repeatable process instead of treating a successful import as finished work.
Keep the page manageable as well as visually faithful.
Explore real editing without changing the shared example.
Understand access before connecting a website.
Resolve common failures without losing the current draft.
The available tools, their inputs and the boundaries they enforce.