Blog / Product

WordPress MCP adapter: why one server per site does not scale

A WordPress MCP adapter per site means twenty JSON blocks and twenty application passwords. A fleet account is one URL.

A WordPress MCP adapter — Automattic’s remote, a local npx process, a block per site — is the right shape for one blog you own. It is the wrong shape for an agency Tuesday.

What one adapter per site costs you

  • A JSON block copied by hand, twenty times.
  • An application password sitting in a file.
  • Full write, or nothing.
  • No record of what the model did.
  • One question, one site, twenty times.

What a fleet server changes

One plugin per site, paired once. No wp-admin password stored. MCP stays read-only. The dashboard asks before a write. The log keeps site, action, result. Ask once; the answer covers the group.

When the adapter is still fine

A single site, you are the only admin, you accept a local process. The day you add a second client host, the adapter becomes inventory you cannot see. That is the switch. Voir aussi : one hosted server for the fleet.