Connect Claude Code and Cursor
Two ways in — the hosted connector, or the npm package running on your own machine.
Claude Code and Cursor are MCP clients like any other. Both can use the hosted connector, and
both can run the wpreef npm package locally instead.
The hosted connector
Add it by URL and sign in through the browser:
claude mcp add --transport http wpreef https://wpreef.vercel.app/mcpCursor adds remote MCP servers from its own settings; the URL is the same one, and it still
ends in /mcp.
The sites, the credentials and the plan are the ones on your wpreef account. This is the same connector ChatGPT and Claude use.
The local package
The npm package is MIT-licensed and runs on your machine. It holds the credential in your own environment and talks to WordPress directly.
claude mcp add wpreef -e WPREEF_URL=https://example.com -e WPREEF_USER=agent -e WPREEF_PASSWORD="$WPREEF_PASSWORD" -- npx -y wpreefFor more than one site, write ~/.wpreef/config.json and keep the passwords in environment
variables:
{
"defaultSite": "blog",
"toolsets": ["core", "content", "media", "design", "blocks"],
"sites": {
"blog": { "url": "https://blog.example.com", "user": "wpreef-agent", "passwordEnv": "WPREEF_BLOG_PW" },
"prod": { "url": "https://example.com", "user": "agent", "passwordEnv": "WPREEF_PROD_PW", "readOnly": true }
}
}Then check the setup before you connect anything:
npx wpreef doctor
npx wpreef doctor --add https://example.comdoctor validates the config, probes every site and prints what each credential can do.
--add walks the onboarding: it prints the authorize link, verifies the result and saves it.
Why this matters
The local package has no action allowance to spend. The 10-action allowance on the Free tier belongs to the hosted connector, which is the part that is sold. The package and the companion plugin are free and stay free.
Which one to use
Use the local package when the machine already holds the credential and you want no third party in the path. Use the hosted connector when you want the same sites inside ChatGPT and claude.ai as well, without a process running anywhere.
Two differences are worth knowing. The hosted connector never offers the admin or raw
toolsets and forces policy.allowUrlFetch off, whatever the stored site row says. The local
package will offer them if you switch them on deliberately.