Multi-Site WordPress MCP Setup – Project Log & Resumption Guide

Overview #

This document records the work carried out to extend Claude’s WordPress MCP connection from a single site (martinpavion.com) to all four WordPress websites. The project has been paused. This guide contains everything needed to resume and complete it.

Background – The Three MCP Components #

Before resuming, understand that three components are involved and they are not redundant – each has a distinct role:

• Braindump MCP plugin – A WordPress plugin installed on the server side of each site. It exposes all site data and features (posts, bookings, courses, backups, SEO, etc.) via a REST API. Without this, Claude has no way to read or write to the site.
• WordPress MCP – The Claude-side connector. It talks to the Braindump plugin on martinpavion.com. Think of Braindump as the server and WordPress MCP as the client. You need both.
• Elementor MCP – A completely separate connection for visual page building inside Elementor. Not covered by Braindump. Must be kept regardless of what happens to the other two.

What Has Been Done #

1. Confirmed the existing WordPress MCP connection to martinpavion.com is working correctly, with 100+ abilities available (content, LatePoint bookings, LearnDash courses, UpdraftPlus backups, SEO, analytics, etc.).
2. Established that extending to multiple sites requires either multiple MCP connectors (not natively supported) or a custom multi-site MCP server.
3. Chose the single multi-site MCP server approach: one Node.js server handles all four sites via a site parameter on each tool call.
4. Built and saved a complete, ready-to-use Node.js MCP server package to the outputs folder. Files produced:
   • multi-wp-mcp/server.js – Main MCP server. Auto-discovers all abilities from the default site on startup, then routes calls to any configured site.
   • multi-wp-mcp/sites.json – Configuration template. Fill in URL and API key per site. No code changes needed to add or remove sites.
   • multi-wp-mcp/package.json – Node.js dependencies (only two: @modelcontextprotocol/sdk and axios).
   • multi-wp-mcp/README.md – Full setup walkthrough, troubleshooting table, and Claude Desktop config snippet.
5. Manually copied all three plugins (Braindump, WordPress MCP adapter, Elementor MCP) to all other WordPress websites. Plugins are installed but NOT yet activated on the new sites.

What Still Needs to Be Done #

Complete these steps in order when resuming the project.

Step 1 – Activate Braindump on each new site #

Go to WordPress Admin → Plugins on each of the three new sites and activate the Braindump MCP plugin. The other two plugins (WordPress MCP adapter, Elementor MCP) do not need to be activated on the new sites – they are Claude-side connectors, not WordPress plugins. Only Braindump is a true WordPress plugin.

Step 2 – Get the API key from each site #

Once Braindump is active on a site, go to its settings page in WordPress Admin and copy the API key. You will need one key per site.

Step 3 – Fill in sites.json #

Open multi-wp-mcp/sites.json and replace the placeholder values with real site URLs and API keys. Give each site a short lowercase key (e.g. guidedhealing, site3). The defaultSite should remain martinpavion.

Step 4 – Install Node.js dependencies #

Run npm install inside the multi-wp-mcp folder. This only needs to be done once.

Step 5 – Verify the REST API endpoint #

The server defaults to /wp-json/braindump-mcp/v1 as the API base. Verify this is correct by visiting https://yoursite.com/wp-json/ in a browser and checking the namespace. Update apiBase in sites.json if it differs.

Step 6 – Test the connection #

Run the test curl command from the README against each new site to confirm the API key and endpoint are correct before wiring Claude up.

Step 7 – Add to Claude Desktop config #

Open the Claude Desktop config file and add the wordpress-multi MCP server entry as shown in the README. Use the full absolute path to server.js.

Step 8 – Restart Claude Desktop and test #

After restarting, ask Claude to list posts from one of the new sites using the site parameter. Confirm it works for each site.

Step 9 (optional) – Retire the old single-site WordPress MCP #

Once the multi-site server is confirmed working for martinpavion.com as well, the original single-site WordPress MCP connector can be removed from the Claude Desktop config to avoid duplication. This is optional – both can coexist.

Key Technical Notes #

• The multi-site server code lives in the Cowork outputs folder. If you need to find it, ask Claude: “Where is the multi-wp-mcp folder?”
• Tool names in the multi-site server follow the pattern wp_namespace__ability_name (e.g. wp_braindump__list_posts, wp_latepoint__list_bookings).
• Adding a fifth or sixth site in future requires only editing sites.json – no code changes.
• Elementor MCP is unaffected by any of this work and should not be touched.
• Node.js 18 or higher is required on the machine running Claude Desktop.

Status at Time of Pausing #

Date paused: 22 April 2026

Blocker: None – project paused by choice, not by a technical issue.

Next action when resuming: Step 1 above – activate Braindump on each new site and collect the API keys.