Download

Multiple sites

Each WordPress site is its own MCP server with its own token. Give each one a clear name, and your assistant can work on one site, compare two, or repeat the same job across all of them.

On this page

One server per site

Every site needs the plugin and a token of its own: a token is signed by the site’s own secret and names the site as its issuer, so a token from one site never works on another. On your computer, each site becomes one entry in your AI client’s MCP configuration, with its own name.

JSON · two sites
{
  "mcpServers": {
    "studio-nord": {
      "command": "claude-wp-mcp",
      "env": { "WPCB_SITE": "https://studio-nord.example", "WPCB_TOKEN": "TOKEN_FOR_STUDIO_NORD" }
    },
    "studio-nord-staging": {
      "command": "claude-wp-mcp",
      "env": { "WPCB_SITE": "https://staging.studio-nord.example", "WPCB_TOKEN": "TOKEN_FOR_STAGING" }
    }
  }
}

With Claude Code, add each one with claude mcp add:

Terminal
claude mcp add --scope user studio-nord -- claude-wp-mcp --site https://studio-nord.example --token TOKEN_FOR_STUDIO_NORD
claude mcp add --scope user studio-nord-staging -- claude-wp-mcp --site https://staging.studio-nord.example --token TOKEN_FOR_STAGING

With Xaflo Desktop 2.0 you don’t write these by hand. In Sites, Add site asks for the address, the token and the Name in Claude Code, and writes the entry for Claude Code with the built-in MCP server. For other apps, the site’s sheet has Set up Claude and ChatGPT.

Working with several sites in Xaflo Desktop

  • The site switcher at the top of the sidebar picks the site that Remote and Library work on; Ctrl+N adds a site.
  • Sites shows which sites answer and which need attention, with Test all. Actions across several sites, such as deploying one plugin to many, live there too.
  • Each site’s sheet has Instructions for the AI: a briefing about that site, with its name and tools, to paste into a new chat. It never contains the token.

Name sites so you can say them

The entry name is how you refer to a site in a prompt, and it becomes part of every tool name. In Claude Code the tools of studio-nord appear as mcp__studio-nord__wp_list_posts, mcp__studio-nord__wp_set_seo and so on.

  • Use short, lowercase names with hyphens: studio-nord, caffe-aurora.
  • Mark environments in the name: -staging, -dev.
  • Keep one name per site. Two entries pointing at the same site with different tokens confuse both you and the assistant.

Prompts across sites

On studio-nord, list the five most recent drafts.

Calls
mcp__studio-nord__wp_list_posts

Compare the active plugins on studio-nord and studio-nord-staging and tell me what differs.

Calls
wp_list_plugins ×2

On every connected site, run a health check and give me one table: site, plugin version, WordPress version, PHP version.

Calls
wp_health_check ×N

When a prompt names no site and several are connected, a good assistant asks which one you mean. Name it anyway; it is faster.

Different sites, different permissions

Because each site has its own token, each can have its own scopes. A common setup: full write access on staging, read-only on production, and a short-lived token with content:publish only on the days you publish. See sets that work.

Desktop Lite and Pro

The plugin and the MCP server work with any number of sites. Xaflo Desktop’s free edition, Desktop Lite, manages 1 site; WP Xaflo Pro manages any number of sites and adds actions across several sites at once. What each edition includes is on the Pricing page.

Staging copies and migrations

A token is valid only for the site address that issued it. When you clone a site to staging, or move it to a new domain, create new tokens on the copy; the old ones will be refused with an issuer mismatch.