A WordPress MCP server is the URL your client calls. In Claude or Cursor you add one server, not twenty. The block is a URL and a bearer token. We host the process. You do not run npx on a laptop that goes to sleep.
What you paste
The dashboard shows the mcp.json fragment: url https://app.getwpmcp.com/mcp and an Authorization header. No WordPress application password. No fleet.yml. The inventory lives on the account after each site is paired.
What the server is allowed to do
Read. List sites, versions, plugins, the last SEO report already stored. It does not update a plugin, block an IP, or flush cache. Those writes go through the dashboard, with a recap you confirm.
Why this is safer than a local server
A local WordPress MCP server usually holds an application password with write scope. If the file leaks, the site is open. A hosted relay holds a pairing token, hashed. Revoke it from the account. The site password never left WordPress.
