Bridge your AI clients — Claude, Cursor, Cline, ChatGPT, Gemini and more — directly to your WordPress sites. Secure, private, and session-less.
connectMWP is a decentralized Model Context Protocol (MCP) bridge that links your AI clients — such as Claude Desktop, Claude Code, Cursor, Cline, ChatGPT, and Gemini/Antigravity — directly to your self-hosted WordPress site, enabling automated content publishing workflows. The project is completely open source; you can find the source repository on GitHub (opens in new window).
connectMWP supports three connection methods, and the plugin's Settings → connectMWP page walks you through whichever one your client needs:
1. Claude Desktop, Claude Code, Cursor, Cline (and other stdio MCP clients) — pair once using a small local client and a cryptographic device key. This is the most secure path (every request is individually signed; see below).
2. ChatGPT — connect remotely by adding connectMWP as a connector and signing in with OAuth. No local install required.
3. Antigravity, Gemini CLI, and other remote MCP clients — connect remotely using a per-site API token that you generate (and can revoke) in your WordPress settings.
You can connect as many clients as you like, and revoke any of them at any time.
Yes. All requests and credentials bypass our servers entirely — the connection runs straight from your AI client to your own WordPress site over HTTPS.
For device-key clients (Claude, Cursor, Cline), connectMWP uses strong cryptography:
Remote clients that can't run the local signer (ChatGPT, Gemini, Antigravity) instead use a revocable, per-site OAuth connection or API token. Whichever method you use, you have full, absolute control — revoke or delete any connected client from your WordPress settings page, and all future access stops immediately.
No. For desktop clients, the MCP server runs via standard input/output (stdio) directly inside your AI client (e.g. Claude) — it does not listen on local network ports, which avoids firewall and antivirus issues. Remote clients (ChatGPT, Gemini, Antigravity) need nothing installed locally at all; they connect straight to your site.
Standard WordPress API calls and logins are often policed or blocked by WAFs, 2FA requirements, and edge proxies (like SiteGround Security, Sucuri, Kinsta, or Cloudflare). connectMWP avoids these problems by operating session-less — it never logs in a user session or uses cookies, and instead authorizes each request directly (by cryptographic signature, OAuth token, or API token). Because there is no login session, 2FA prompts never intercept the connection, and the integration keeps working alongside your security plugins instead of being blocked by them.
Yes! connectMWP supports multi-site configurations. For desktop clients you register the local client once and add multiple domains via the `add-site` CLI helper, then target a specific site using the optional `site` parameter. Each site is paired independently, so a key or token for one site never grants access to another.
connectMWP is 100% free and open source. There are no monthly subscriptions, no usage tiers, and no central API proxy costs. Since your AI client communicates directly with your own WordPress server, you never pay middleware fees — you just use your existing AI subscription (such as Claude Pro/Team or ChatGPT).
On the WordPress side (always required):
On your computer (only for desktop / stdio clients — Claude Desktop, Claude Code, Cursor, Cline):
ChatGPT, Gemini CLI, and Antigravity connect to your site remotely and need no local install — you add connectMWP as a connector (ChatGPT signs in with OAuth; Gemini/Antigravity use a per-site API token).
*Note: You do not need to install Next.js or build this website locally. Next.js only powers this public guide; the local client runs purely on lightweight, native Node.js.*
Open your computer's terminal (Terminal on macOS, or Command Prompt/PowerShell on Windows) and run:
```bash
node -v
npm -v
```
If these commands print version numbers (e.g., `v18.x.x` or higher), you are ready.
If they print "command not found" or similar errors:
1. Download the LTS (Long Term Support) version of Node.js from the official Node.js Website and run the installer.
2. Restart your terminal window and run the commands again to verify the installation.