Connect another MCP client
Use OAuth when supported, or a scoped manual token.
Before you connect
Pair a WordPress site in AI2WP first. During early access, your account needs an invitation, an active paid license or owner access. Your AI provider controls which plans and workspaces can add custom connectors.
Set up the connection
Follow these steps in the client you use. Interface labels may vary as providers update their products.
- Check that your client supports remote Streamable HTTP MCP and OAuth with PKCE and dynamic client registration. Add the URL below and complete browser authorization.
- If it only supports bearer tokens, create one in MCP connections → Manual tokens. Configure Authorization: Bearer YOUR_TOKEN in the client’s private credential settings. Never paste it into a chat.
- Verify the site with a read-only request first. Client support for files, browser rendering and complex tool calls varies; a successful connection does not certify the full conversion workflow.
Verify the destination
List my authorized AI2WP sites. Ask me which domain to use, then inspect that site and report its domain and plugin version. Pass its site_id on every subsequent call. Do not create or modify any page.
What this connection can do
Read and inspect allowed WordPress pages. With draft-editing access, run the supported draft creation and editing operations. It cannot publish, manage arbitrary plugins or bypass your account’s domain or conversion allowance. Full visual conversion also needs file handling, rendering and editor checks; the provided workspace currently targets Codex and Claude Code.
If it does not connect
Missing connector controls usually mean a provider plan or workspace restriction. If approval expires, start again from your AI client. If AI2WP reports no eligible sites, finish pairing and confirm invitation or paid access. Revoke an old connection from MCP connections before replacing it.
Official Other clients documentation
All connection methods