BeTheme MCP Server

A secure, agent-friendly MCP server designed to operate a WordPress site running BeTheme as a full backend-equivalent environment.

┌──────────────────────────────────────────────────────────────┐
│  BeTheme MCP Server                                       │
│  Agent-driven WordPress + BeTheme administration           │
│  Pages • Templates • Plugins • WooCommerce • BeBuilder     │
└──────────────────────────────────────────────────────────────┘

What this project does

This project aims to let an AI agent manage a BeTheme-powered WordPress site without needing to log in through a browser. The MCP layer is intended to support:

• building and editing pages in BeBuilder

• creating and configuring templates for headers, footers, archives, product pages, and other BeTheme layouts

• installing, activating, updating, and configuring plugins

• working with WooCommerce and related ecosystem plugins

• handling site administration in a secure, auditable, and capability-aware way

Related MCP server: WooCommerce MCP Server

Why this matters

The native WordPress MCP experience is not sufficient for BeTheme because BeTheme uses its own builder architecture and custom page/template model. This project bridges that gap so an agent can work with the site in a way that feels close to working directly in the WordPress backend.

Installation

Prerequisites

• Node.js 22 or newer

• npm

• A WordPress site with the BeTheme bridge plugin installed

Local setup

1. Clone the repository and install dependencies:

   • npm install

2. Create a local environment file from the example:

   • cp .env.example .env

3. Configure the bridge connection values in .env:

   • BETHEME_MCP_API_KEY=replace-with-a-secure-key

   • BETHEME_MCP_BASE_URL=http://your-wordpress-site.test

4. Start the MCP server:

   • npm start

5. Optional: run the local demo harness:

   • npm run demo

WordPress bridge plugin

1. Copy the plugin folder from plugin into your WordPress installation's wp-content/plugins/ directory.

2. Activate the plugin from the WordPress admin dashboard.

3. Set the same API key in the WordPress environment that the MCP server uses.

Documentation

The project documentation is organized under the docs folder:

• docs/README.md — documentation index

• docs/sdd/01-overview.md — product overview

• docs/sdd/02-architecture.md — system architecture

• docs/sdd/03-data-model-and-workflows.md — data model and workflows

• docs/sdd/04-implementation-plan.md — implementation plan

• docs/sdd/05-requirements-coverage.md — requirement mapping

• docs/sdd/06-security-and-owasp.md — security posture

• docs/sdd/07-mcp-capability-surface.md — MCP tools, resources, and prompts

• docs/tdd/01-test-strategy.md — testing strategy

• docs/tdd/02-test-cases.md — test cases

• docs/tdd/03-execution-checklist.md — execution checklist

Security first

This project is intended for high-risk administrative use. The design explicitly calls for:

• strong authentication and authorization

• least-privilege access

• audit logging

• input validation and payload hardening

• OWASP-aligned security controls

Repository focus

This repository currently contains the project documentation and the BeTheme research context needed to guide implementation. The next step is to turn that specification into the actual MCP server and bridge components.

Release and versioning

The project ships through GitHub releases with versioning aligned to the BeTheme version it targets. The first alpha release is version 28.5.4-alpha.001, which keeps the BeTheme version reference of 28.5.4 and clearly marks the package as the first alpha build.

Alpha release notice

This project is currently an alpha release and is still under quality assurance. It is intended for evaluation, integration testing, and controlled internal use, not for production deployment until QA is complete.

Status

Status: core MCP runtime, bridge routes, and test coverage are now implemented and verified locally. The current release is alpha and remains in QA.